[Ffmpeg-devel-irc] ffmpeg-devel.log.20170611

burek burek021 at gmail.com
Mon Jun 12 03:05:03 EEST 2017


[02:29:21 CEST] <cone-194> ffmpeg 03Michael Niedermayer 07master:71da0a5c9750: avcodec/ra144: Fix runtime error: signed integer overflow: -2200 * 1033073 cannot be represented in type 'int'
[02:29:21 CEST] <cone-194> ffmpeg 03Michael Niedermayer 07master:1197c0489642: avcodec/fft_template: Fix multiple runtime error: signed integer overflow: -1943918714 - 1935113003 cannot be represented in type 'int'
[02:29:21 CEST] <cone-194> ffmpeg 03Michael Niedermayer 07master:22a25ab3896c: avcodec/tiff: Fix leak of geotags[].val
[03:45:10 CEST] <thebombzen> hmm... how long does it usually take a developer to take a look at a crash bug on TRAC?
[10:02:22 CEST] <cone-423> ffmpeg 03Paul B Mahol 07master:29bdcf588f81: avcodec: add Gremlin DPCM decoder
[10:02:22 CEST] <cone-423> ffmpeg 03Paul B Mahol 07master:d1c08027d8e4: avcodec: add Gremlin Digital Video decoder
[10:02:22 CEST] <cone-423> ffmpeg 03Paul B Mahol 07master:c94841487622: avformat: add Gremlin Digital Video demuxer
[10:27:42 CEST] <cone-423> ffmpeg 03Paul B Mahol 07master:9a949cdf8f6c: avcodec/gdv: fix compiler warnings
[13:27:03 CEST] <kierank> thebombzen: infinity
[13:58:43 CEST] <durandal_1707> kierank: infinity what?
[14:10:10 CEST] <kierank> Infinity times to answer ticket
[14:52:00 CEST] <thebombzen> I was wondering how long it took on average for devs to analyze bugs
[14:52:19 CEST] <thebombzen> I ask because I submitted a bug report 3 weeks ago about a segfault crash
[14:53:18 CEST] <JEEB> depends on if someone cares and/or has looked at the trac if that's where you reported an issue
[15:23:13 CEST] <cone-965> ffmpeg 03Michael Niedermayer 07master:6d499ecef9c2: avcodec/aacdec_fixed: Fix runtime error: left shift of negative value -1297616
[15:23:13 CEST] <cone-965> ffmpeg 03Michael Niedermayer 07master:2e44126363bc: avcodec/snowdec: Fix runtime error: left shift of negative value -1
[17:32:23 CEST] <thebombzen> JEEB: it's on trac yea
[17:32:57 CEST] <thebombzen> a bit disappointed b/c I spent a bit of time trying to run valgrind and all
[17:52:23 CEST] <JEEB> thebombzen: well I can't say much not knowing what this thing is :)
[17:52:52 CEST] <thebombzen> this is the ticket
[17:52:53 CEST] <thebombzen> https://trac.ffmpeg.org/ticket/6413
[17:53:22 CEST] <JEEB> right
[17:56:15 CEST] <JEEB> well, I have this feeling that the ssh stuff was just added by someone and nobody has the intent of actually maintaining it. plus not many people actually look at the trac too much. so if you actually have use cases for it, you might want to see if you want to maintain it.
[19:51:49 CEST] <thebombzen> this is one of those bugs I would fix provided that I could debug C memory errors
[19:51:55 CEST] <thebombzen> but I don't know C well enough for that
[19:53:42 CEST] <jamrial> thebombzen: just sent a fix to the ml
[19:54:03 CEST] <nevcairiel> the ML doesnt think so!
[19:55:02 CEST] <thebombzen> lol okay thanks
[19:55:37 CEST] <jamrial> nevcairiel: huh, you're right, it's not in the archives
[19:58:44 CEST] <nevcairiel> there it is
[19:58:51 CEST] <nevcairiel> was just slow
[20:29:11 CEST] <cone-630> ffmpeg 03James Almer 07master:e3887c0a2c57: avformat/mov: add support for reading VP Codec Configuration Box
[20:53:58 CEST] <cone-630> ffmpeg 03Michael Niedermayer 07master:c996374d4d86: avcodec/wavpack: Fix runtime error: signed integer overflow: 1886191616 + 277872640 cannot be represented in type 'int'
[20:53:59 CEST] <cone-630> ffmpeg 03Michael Niedermayer 07master:d24043e1a2f9: avcodec/jpeg2000dwt: Fix runtime error: left shift of negative value -123
[20:55:26 CEST] <BtbN> oh, nice. Those efforts to not link, not strip and --disable-doc on coverity actually cut off like 12 minutes from the build time
[22:45:06 CEST] <BBB> thebombzen: within a couple of days usually
[23:37:21 CEST] <durandal_1707> michaelni: having random numbers in logs is not useful
[00:00:00 CEST] --- Mon Jun 12 2017


More information about the Ffmpeg-devel-irc mailing list