[Ffmpeg-devel] Re: [BUG] Compilation failure when using --disable-opts
Fri Mar 16 23:15:09 CET 2007
M?ns Rullg?rd escreveu:
> Diego Biurrun <diego at biurrun.de> writes:
>> On Thu, Mar 15, 2007 at 08:03:58PM -0300, Ramiro Polla wrote:
>>> M?ns Rullg?rd escreveu:
>>>> Panagiotis Issaris <takis at issaris.org> writes:
>>>>> Sure. Although I wonder: Doesn't anybody in here use a debugger? Aren't
>>>>> you annoyed by the jumping around because of reorderings caused by the
>>>>> compilers' optimizations?
>>>> That's what makes debugging fun. It gets even better on MIPS with
>>>> delayed branching...
>>>> Actually, I don't use debuggers a whole lot. I find a generous
>>>> measure of printf works much better in most cases.
>>> You should try Microsoft Visual Studio =) It will totally change your
>>> debugging experience.
>>> (yes, I know. It doesn't debug .stabs..)
>> IIRC Mans knows Visual Studio.
> I have probably used more debuggers than most of you, none of them
> particularly impressive, and Visual Studio worse than most.
Hmm... I found it way better than any gdb based front-end like ddd,
insight, kdbg, code::blocks...
Could you point which one you prefer when you must use one? I'm curious
as to why it is worse than most.
> What I'm trying to get at is that a debugger might often let you see a
> snapshot of the process state whenever you stop it, typically at a
> breakpoint. What it will not do is tell you how the process got into
> that state. Placing print statements in strategic places will produce
> a log telling you exactly what has happened. The trick is in printing
> the right information at the right places.
Sure, I prefer printfs to corner down the bug. But then, if it's not
clear yet, I use a debugger to step into the code and find out exactly
what's going wrong.
>> May I take bets who is going to survive the upcoming flamewar unscathed?
> What war?
More information about the ffmpeg-devel