On Thu Jul 24 3:21 +0200, J.A. Magallon wrote: > I have read through manuals and they say that signals 32+ are 'real time > signals', and that linuxthreads use the first 3 internally. And that > gdb should not stop the app with one of that signals, to debug MT apps.
as a temporary workaround, try: handle SIG32 nostop pass noprint in gdb. > I suppose that the hang point in gdb is not the real one, gdb stops there > and should not do it. > > Problem with glibc build ? With gdb ? > If someone guesses why gdb hangs, then I would try to see what makes my > code hang... I've basically given on using gdb in current cooker... BTW, which package provides gdb? # rpm -qf `which gdb` file /usr/bin/gdb is not owned by any package -- Levi Ramsey [EMAIL PROTECTED] [EMAIL PROTECTED] Take due notice and govern yourselves accordingly. Currently playing: Corrosion of Conformity - Wiseblood - Born Again fo Linux 2.4.21-3mdk 21:55:00 up 1 day, 8:56, 11 users, load average: 0.08, 0.08, 0.07
