[vlc-devel] Re: Help on VLC - KDevelop debugging issues

Paul Forgey paulf at aphrodite.com
Tue Jun 10 23:49:38 CEST 2003

Isn't KDevelop's debugger a gdb front-end?  At least on Linux, a 
process takes for-ev-er to load a shared library when it is being 

Not to turn this thread into discussion about how to use gdb, but I 
have a similar question about debugging the modules.  How the heck does 
one set breakpoints on a module's initialization code?  If the process 
isn't running, gdb can't re-establish breakpoints in shared libraries 
when you do run the process, and by the time the shared libraries are 
loaded and the breakpoints can be set, it's too late..

On Tuesday, June 10, 2003, at 02:42 PM, Cyril Deguet wrote:

> On Mon, Jun 09, 2003, Bentzy Sagiv wrote:
>> 1) It takes a lot of time until the VLC window (GUI) opens (20-25 
>> minutes)
>> 	(in the meantime it runs inside different *.so files).
> I don't know if it's possible with kdevelop, but with gdb we can use 
> the
> following trick to speed up debugging:
> - run vlc with rc interface
> - attach gdb to the running process
> - launch the GUI with the rc interface (e.g "intf skins")
> But once again I don't know if kdevelop can attach its debugger to a
> running process, and handles threads correctly.

This is the vlc-devel mailing-list, see http://www.videolan.org/vlc/
To unsubscribe, please read http://developers.videolan.org/lists.html
If you are in trouble, please contact <postmaster at videolan.org>

More information about the vlc-devel mailing list