From: Andreas Schwab <schwab@suse.de>
To: Klaus Zeitler <kzeitler@lucent.com>
Cc: gdb@sources.redhat.com, gdb-patches@sources.redhat.com
Subject: Re: gdb output problems when run in shell (bash or ksh)
Date: Tue, 02 Aug 2005 11:51:00 -0000 [thread overview]
Message-ID: <jeoe8g36c6.fsf@sykes.suse.de> (raw)
In-Reply-To: <q5gfytsww07.fsf@lucent.com> (Klaus Zeitler's message of "Tue, 02 Aug 2005 11:03:52 +0200")
Klaus Zeitler <kzeitler@lucent.com> writes:
> 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.:
Does this patch help?
2005-08-02 Andreas Schwab <schwab@suse.de>
* sol-thread.c (sol_thread_wait): Call target_terminal_ours before
printing output.
--- gdb/sol-thread.c.~1.50.~ 2005-06-27 10:03:40.000000000 +0200
+++ gdb/sol-thread.c 2005-08-02 13:46:35.000000000 +0200
@@ -463,6 +463,7 @@ sol_thread_wait (ptid_t ptid, struct tar
&& !ptid_equal (rtnval, save_ptid)
&& !in_thread_list (rtnval))
{
+ target_terminal_ours ();
printf_filtered ("[New %s]\n", target_pid_to_str (rtnval));
add_thread (rtnval);
}
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, MaxfeldstraÃe 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2005-08-02 11:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-02 9:04 Klaus Zeitler
2005-08-02 11:51 ` Andreas Schwab [this message]
2005-08-02 13:57 ` Klaus Zeitler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jeoe8g36c6.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=gdb-patches@sources.redhat.com \
--cc=gdb@sources.redhat.com \
--cc=kzeitler@lucent.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).