Author Topic: C::B debugging, but gdb/gcc in chroot?  (Read 3341 times)

Vladsharp

  • Guest
C::B debugging, but gdb/gcc in chroot?
« on: June 21, 2007, 02:54:12 pm »
Hi all,

I've got a question about using gdb to debug chrooted executables. In detail: I'm running Gentoo with gcc 4.2.0 (for which there is no gdc [gcc d compiler] available yet) - so naturally, I have a chroot for various applications that can be considered more *stable* (old, in other words...) than my main system. Now, I know I could probably install the relevant X libraries, wxPython, etc.. to the chroot, but that will be wasteful (from the space perspective). All that Code::Blocks should be able to do, is basically connect to a running instance of gdb and that way I can debug my programs. Is that possible? I could of course start switching gcc version on my main box, but there's two problems: I won't be able to start some programs until I switch back to gcc 4.2 (using gcc-config , btw.) and the main system has some very mean C{XX}FLAGS/LDFLAGS which pretty much render debugging useless...

:)