Public bug reported:
This concerns debugging with gtk 2.10.11 libraries.
The library "disturbs" the debugger gdb ( version GNU gdb 6.6-debian ).
I don't know if it's only on multithread apps but here is what happens : As
soon as you add the gtk libs even to the most simple program, the debugger
returns a weird message just as soon as it enters the main function.
Something like :
(gdb) run
Starting program: "whatever"
[Thread debugging using libthread_db enabled]
[New Thread -1218099520 (LWP 30755)]
[Switching to Thread -1218099520 (LWP 30755)]
then it goes through the code but right after the "clone()" call it shows
something like :
[New Thread -1218099520 (LWP -1)]
Can't attach LWP -1: No such process
then it generates some warning of instability and you have to close the
debugger.
If the program is't linked with the gtk libs it works fine ( i mean the
debugger works -the program doesn't seem to crash in any case ( all
these concern the debugging process )). I did not try to see wich
particular library crashes ( i use pkg-config). Of course i need the
libs in the real program, this is just a dummy application i've tested.
Anyway i'm trying some workarounds now. It seems that gtk 1.2 doesn't
crash but i'm not in the mood for switching over to an older package it
would mean to much trouble allthough it might be the safest thing to do.
Ideas?
Thnx.
** Affects: ubuntu
Importance: Undecided
Status: New
--
gtk. 2.10.11 debuggig
https://bugs.launchpad.net/bugs/153645
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
