Re: gdb & gtk+: Cannot find new threads: generic error

["aniket ray" <aniket ray gmail com>]

On Tue, Dec 16, 2008 at 4:25 AM, knocte <knocte gmail com> wrote:
> Hello. I have a wierd gdb problem which is only reproducible with some
> gtk programs but not all of them.
>
> For example, gedit works perfectly:
>
> knocte111 linux-jsnn:~> gdb gedit
> GNU gdb (GDB; openSUSE:11.1) 6.8.50.20081120-cvs
> Copyright (C) 2008 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later
> <http://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
> and "show warranty" for details.
> This GDB was configured as "i586-suse-linux".
> For bug reporting instructions, please see:
> <http://bugs.opensuse.org/>...
> (gdb) run
> Starting program: /usr/bin/gedit
> [Thread debugging using libthread_db enabled]
> [New Thread 0xb35d9b90 (LWP 5765)]
>
> After that, I see the new window of gedit appearing.
>
> However, this doesn't work for gtk-demo:
>
> knocte111 linux-jsnn:~> gdb gtk-demo
> GNU gdb (GDB; openSUSE:11.1) 6.8.50.20081120-cvs
> Copyright (C) 2008 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later
> <http://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
> and "show warranty" for details.
> This GDB was configured as "i586-suse-linux".
> For bug reporting instructions, please see:
> <http://bugs.opensuse.org/>...
> (gdb) run
> Starting program: /usr/bin/gtk-demo
> [Thread debugging using libthread_db enabled]
> Error while reading shared library symbols:
> Cannot find new threads: generic error
> Cannot find new threads: generic error
> (gdb) quit
> The program is running.  Quit anyway (and kill it)? (y or n) y
>
>
>
> Any ideas why this happens?
>
Don't know the real solution. But I have faced this plenty of times.
Continuing (just type c)  from the point where it stopped should
continue the program as if nothing happened.


> Thanks very much,
>
>        Andrés
>

Thanks,
Aniket Ray