[vlc-devel] Re: Compile VLC for debugging
stondage123 at yahoo.com
Sun May 20 18:40:37 CEST 2007
Ok. How do you debug the code then? GDB is pretty useless with optimized code. Do you guys use tracing of some sort? I'd really like to be able to step through the code. Any help would be appreciated.
Thanks for the info,
----- Original Message ----
From: Felix Paul Kühne <fkuehne.videolan at googlemail.com>
To: vlc-devel at videolan.org
Sent: Sunday, May 20, 2007 12:34:32 PM
Subject: [vlc-devel] Re: Compile VLC for debugging
Am 20.05.2007 um 17:24 schrieb Andrew Stone:
> I'd also like to know.
> ./configure --enable-debug --disable-optimizations
> doesn't disable optimizations for some reason.
That's correct. The debug flag works as expected (it adds debug info,
etc.), but -optimizations is a bit useless, as VLC's code is always
being optimised with our current build system without having the
possibility to change the level by hand. You can only specifically
disable the usage of AltiVec optimisations (for PowerPC CPUs) and
additionally, you may optimise for memory usage (--enable-optimize-
> ----- Original Message ----
> From: Herman Schultz <herman.schultz at gmail.com>
> Can you please tell me how can i compile VLC for debugging and how
> can I run VLC to run under a debugger?
We recommend you to use gdb for debugging VLC. Simply running VLC in
it, is straight forward: "$ gdb ./vlc" (or similar; depending where
your VLC binary is actually located). Using gdb is a bit more
complicated, so please have a look at gdb's documentation.
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