gdb output problems when run in shell (bash or ksh)

[Klaus Zeitler <kzeitler at lucent dot com>]

Hello,

I'm trying to debug a program with more than 100 threads under Solaris 5.8,
that generates lots of output. When I run the program under gdb in bash,
the first few threads are started, then gdb suspends itself and I need to
call 'fg' to resume execution, i.e. the whole thing looks like e.g.:

[674]$ gdb ./umc.vx 
GNU gdb 6.3.0.20050704-cvs
...
[New LWP 27]
UMC1-1-> [07-05 10:05:41:932930] (tMain      ) : Smdev: SMDEV initialization succeeded!
[New LWP 28]
logMsg [07-05 10:05:42:849879] (FireWire   ) : PetDemon create Server socket on port 45263
UMC1-1-> [07-05 10:05:42:870024] 0x13dd7d0  (tFtpdTask  ) : waiting for a new client connection...
UMC1-1-> [07-05 10:05:42:981463] 0x7277b0   (tMain      ) : Initializing OSipc

[6]+  Stopped                 gdb ./umc.vx
[675]$ fg
gdb ./umc.vx
---Type <return> to continue, or q <return> to quit---
[New LWP 29]
logMsg [07-05 10:20:36:924936] (nbapDemon  ) : PetDemon create Server socket on port 45260
...


When run in ksh, gdb isn't put in background. Instead after quite a few lines
of output from the image interspersed with gdb output lines "[New LWP <nn>]",
ksh seems to hang. Top then shows that both gdb and ksh are both running at
approximately 50% CPU.

But when I run the program in emacs or ddd, I don't have any problems.  Since
this always happens while gdb is trying to print more than 200 times "[New LWP
<nn>]", maybe we have a problem with both gdb and the image printing at the
same time.

I'd appreciate any help. Thanks

Klaus

-- 
 ------------------------------------------
|  Klaus Zeitler      Lucent Technologies  |
|  Email:             kzeitler@lucent.com  |
 ------------------------------------------
---
Our policy is, when in doubt, do the right thing.
    -- Roy L. Ash, ex-president Litton Industries