From: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
To: drow@false.org
Cc: gdb-patches@sources.redhat.com
Subject: Re: remote debugging a multi-threaded program with signal
Date: Fri, 19 Mar 2004 00:09:00 -0000 [thread overview]
Message-ID: <20040305.131748.104026850.nemoto@toshiba-tops.co.jp> (raw)
In-Reply-To: <20040304222800.GA29911@nevyn.them.org>
>>>>> On Thu, 4 Mar 2004 17:28:00 -0500, Daniel Jacobowitz <drow@false.org> said:
> * infrun.c (handle_inferior_event): Pass nostop signals to the
> correct thread.
...
> - if (printed)
> - target_terminal_inferior ();
> -
BTW, it would be better to move those lines to the preceding #if 0 block? :-)
/* ??rehrauer: I don't understand the rationale for this code. If the
...
For now, remove the message altogether. */
#if 0
printed = 1;
target_terminal_ours_for_output ();
printf_filtered ("\nProgram received signal %s, %s.\n",
target_signal_to_name (stop_signal),
target_signal_to_string (stop_signal));
gdb_flush (gdb_stdout);
#endif
---
Atsushi Nemoto
WARNING: multiple messages have this Message-ID
From: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
To: drow@false.org
Cc: gdb-patches@sources.redhat.com
Subject: Re: remote debugging a multi-threaded program with signal
Date: Fri, 05 Mar 2004 04:15:00 -0000 [thread overview]
Message-ID: <20040305.131748.104026850.nemoto@toshiba-tops.co.jp> (raw)
Message-ID: <20040305041500.4vpPRPHqSMCNIQOvSYwXTxL2utCICKwy0t8voRU7dfA@z> (raw)
In-Reply-To: <20040304222800.GA29911@nevyn.them.org>
>>>>> On Thu, 4 Mar 2004 17:28:00 -0500, Daniel Jacobowitz <drow@false.org> said:
> * infrun.c (handle_inferior_event): Pass nostop signals to the
> correct thread.
...
> - if (printed)
> - target_terminal_inferior ();
> -
BTW, it would be better to move those lines to the preceding #if 0 block? :-)
/* ??rehrauer: I don't understand the rationale for this code. If the
...
For now, remove the message altogether. */
#if 0
printed = 1;
target_terminal_ours_for_output ();
printf_filtered ("\nProgram received signal %s, %s.\n",
target_signal_to_name (stop_signal),
target_signal_to_string (stop_signal));
gdb_flush (gdb_stdout);
#endif
---
Atsushi Nemoto
next prev parent reply other threads:[~2004-03-05 4:15 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-03 15:59 Atsushi Nemoto
2004-03-19 0:09 ` Atsushi Nemoto
2004-03-19 0:09 ` Atsushi Nemoto
2004-03-04 14:58 ` Atsushi Nemoto
2004-03-04 22:28 ` Daniel Jacobowitz
2004-03-19 0:09 ` Atsushi Nemoto
2004-03-05 2:25 ` Atsushi Nemoto
2004-03-19 0:09 ` Atsushi Nemoto
2004-03-05 16:36 ` Atsushi Nemoto
2004-03-05 16:38 ` Daniel Jacobowitz
2004-03-06 12:42 ` Atsushi Nemoto
2004-03-19 0:09 ` Atsushi Nemoto
2004-03-19 0:09 ` Daniel Jacobowitz
2004-03-06 17:11 ` Daniel Jacobowitz
2004-03-07 14:14 ` Atsushi Nemoto
2004-03-19 0:09 ` Atsushi Nemoto
2004-03-19 0:09 ` Daniel Jacobowitz
2004-03-19 0:09 ` Atsushi Nemoto [this message]
2004-03-05 4:15 ` Atsushi Nemoto
2004-03-19 0:09 ` Daniel Jacobowitz
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=20040305.131748.104026850.nemoto@toshiba-tops.co.jp \
--to=anemo@mba.ocn.ne.jp \
--cc=drow@false.org \
--cc=gdb-patches@sources.redhat.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