Debian GNU/Linux

Comment 5 for bug 219527

Martin Emrich (emme) wrote :

Hi!

Your program works fine, lists all available users. In the same shell just afterwards, hitting "su - po<TAB>" crashes the bash instance (bumps me back to the Box I ssh'd into the server from).
BTW: I upgraded my "real" server over the weekend, and it exhibits the same behaviour as the VM I first encountered this bug in.

I just tried it with gdb, but there are no debug symbols in bash:

(gdb) run
The program being debugged has been started already.
Start it from the beginning? (y or n) y
Starting program: /bin/bash
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
root@sauron:~# su - po(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
Error while reading shared library symbols:
Cannot find new threads: generic error
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
---Type <return> to continue, or q <return> to quit---
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
Cannot find new threads: generic error
(gdb)

Where could I get a bash package with debug symbols?

Ciao

Martin