From: Eli Zaretskii <eliz@gnu.org>
To: Paul_Koning@Dell.com
Cc: gnu@toad.com, tromey@redhat.com, palves@redhat.com,
mark.kettenis@xs4all.nl, brobecker@adacore.com,
gdb@sourceware.org
Subject: Re: Time to expand "Program received signal" ?
Date: Fri, 16 Nov 2012 08:25:00 -0000 [thread overview]
Message-ID: <83r4nurm46.fsf@gnu.org> (raw)
In-Reply-To: <C75A84166056C94F84D238A44AF9F6AD2A2CA1@AUSX10MPC103.AMER.DELL.COM>
> From: <Paul_Koning@Dell.com>
> CC: <tromey@redhat.com>, <palves@redhat.com>, <mark.kettenis@xs4all.nl>, <brobecker@adacore.com>, <gdb@sourceware.org>
> Date: Thu, 15 Nov 2012 22:26:27 +0000
>
> But you didn't address the issue that you can't readily tell whether a program is multi-threaded. It may have had multiple threads but it doesn't now, or it may have more later.
At least on MS-Windows, GDB tells me when a new thread is created.
So it does know. I have no experience with threads on Posix
platforms, so I don't know for sure that the same is possible there.
But the "set print thread-events" command is not Windows-specific, so
I believe the above is also true for Posix platforms.
next prev parent reply other threads:[~2012-11-16 8:25 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-12 18:27 Pedro Alves
2012-11-13 16:25 ` Joel Brobecker
2012-11-13 16:40 ` Mark Kettenis
2012-11-13 17:22 ` Pedro Alves
2012-11-13 22:40 ` John Gilmore
2012-11-14 10:26 ` Pedro Alves
2012-11-14 19:54 ` John Gilmore
2012-11-15 10:36 ` Pedro Alves
2012-11-15 16:58 ` Eli Zaretskii
2012-11-15 17:21 ` Pedro Alves
2012-11-15 17:51 ` Joel Brobecker
2012-11-15 18:16 ` Eli Zaretskii
2012-11-15 18:27 ` Pedro Alves
2012-11-15 19:07 ` Eli Zaretskii
2012-11-15 20:33 ` Pedro Alves
2012-11-15 20:58 ` Eli Zaretskii
2012-11-15 18:27 ` Paul_Koning
2012-11-15 19:27 ` Tom Tromey
2012-11-15 22:21 ` John Gilmore
2012-11-15 22:27 ` Paul_Koning
2012-11-16 0:22 ` John Gilmore
2012-11-16 8:25 ` Eli Zaretskii [this message]
2012-11-13 17:23 ` Joel Brobecker
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=83r4nurm46.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=Paul_Koning@Dell.com \
--cc=brobecker@adacore.com \
--cc=gdb@sourceware.org \
--cc=gnu@toad.com \
--cc=mark.kettenis@xs4all.nl \
--cc=palves@redhat.com \
--cc=tromey@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