[FFmpeg-devel] [PATCH 3/3] Add assert that the avcodec lockisheld when initializing static VLC tables.
donmoir at comcast.net
Wed Dec 5 00:42:33 CET 2012
----- Original Message -----
From: "Reimar Döffinger" <Reimar.Doeffinger at gmx.de>
To: "FFmpeg development discussions and patches" <ffmpeg-devel at ffmpeg.org>
Sent: Tuesday, December 04, 2012 5:45 PM
Subject: Re: [FFmpeg-devel] [PATCH 3/3] Add assert that the avcodec lockisheld when initializing static VLC tables.
> On Tue, Dec 04, 2012 at 06:32:00AM -0500, Don Moir wrote:
>> This is a windows app and no beta testers are going to have any
>> linux / MinGW / Windows debugging tools. The beta testers are not
> I know, I was thinking about an option to include e.g. gdb in
> testing versions, but I think it is overkill.
>> The point about debug dlls for beta testing is to include named
>> functions but not sure that would work. If it did work it doesn't do
>> much good for shipping version.
> Either way, since the users are not developers, they do not need to know
> the names.
The names were never intended for the users. They would not mean anything to a non programmer.
> You skipped my question about what you mean by "debug dll".
> I believe that term is usually used to mean "compiled without
> optimization", which is very different from "compiled with
> debug information" which would be enough.
Typically its either a debug or release build in windows speak and I just figured you knew that.
You can compile either with optimizations on or off using either MS or Intel compiler. The debug build is usually compiled with
optimizations off and includes named symbols etc.
> If you use ASLR (which I hope you do) you might need some tricks
> to figure out the DLL load address and compensate for it.
The main application is not my own and uses some 3rd partly protection scheme. It also handles any exceptions. I can pretty much
deal with it as I generally do have enough info.
Just kind of thinking ahead.
More information about the ffmpeg-devel