[vlc-devel] Re: Compile VLC for debugging
stondage123 at yahoo.com
Mon May 21 15:37:50 CEST 2007
I set optim=no, but that still doesn't work. Values keep being optimized out.
----- Original Message ----
From: Damien Fouilleul <damien.fouilleul at laposte.net>
To: vlc-devel at videolan.org
Sent: Monday, May 21, 2007 5:43:26 AM
Subject: [vlc-devel] Re: Compile VLC for debugging
To debug with GDB, just edit vlc-config and rename optim=yes to
optim=no, and re-build the part of VLC you want to debug.
If like me, you want to use hard-breakpoints, i.e break the program into
the debugger without relying on GDB breakpoints, just add the following
in your code:
- DebugBreak() if you are debugging on Windows
- raise(SIGTRAP) if are debugging on Linux, MacOSX, etc...
Felix Paul Kühne wrote:
> Am 20.05.2007 um 20:24 schrieb Rémi Denis-Courmont:
>> Le dimanche 20 mai 2007, Andrew Stone a écrit :
>>> Ok. How do you debug the code then? GDB is pretty useless with
>>> optimized code.
>> From my experience, gdb is pretty useless with VLC regardless of
>> optimization. I personnaly use valgrind.
> ... while for my needs, gdb has always been sufficient, even with
> optimisations, but I was never able to test valgrind, as it is
> Linux-only for now.
> Felix Paul Kühne
> Co-Developer of VLC's Mac OS X port
This is the vlc-devel mailing-list, see http://www.videolan.org/vlc/
To unsubscribe, please read http://developers.videolan.org/lists.html
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the vlc-devel