[Bug 804131] Re: gdb internal-error: thread_get_info_callback

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: gdb (Ubuntu)
       Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/804131

Title:
  gdb internal-error: thread_get_info_callback

Status in “gdb” package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 10.10
  Intel 32-bit processor
  gdb 7.2-1ubuntu3

  Running my program in gdb, I get:
  warning: Can't attach LWP 1717974884: No such process
  /build/buildd/gdb-7.2/gdb/linux-thread-db.c:392: internal-error: thread_get_info_callback: Assertion `inout->thread_info != NULL' failed.
  A problem internal to GDB has been detected,
  further debugging may prove unreliable.
  Quit this debugging session? (y or n) n

  /build/buildd/gdb-7.2/gdb/linux-thread-db.c:392: internal-error: thread_get_info_callback: Assertion `inout->thread_info != NULL' failed.
  A problem internal to GDB has been detected,
  further debugging may prove unreliable.
  Create a core file of GDB? (y or n) y
  (gdb) 

  I tracked down the offending line, when I comment it out, problem goes away. But the line is seemingly irrelevant nothing more than a strcat() function. 
  I'm attaching a tarball which contains the executable and source code with makefile.
  To compile you will need libnetfilter_queue and libncurses
  To reproduce the bug:
  Run lpfw 2.0 as root (it uses netfilter_queue facility, hence root)
  Run cli2.0 as root and press "s"
  See lpfw2.0 cause such strange gdb's behaviour.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/804131/+subscriptions