From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: Mark Kettenis <mark.kettenis@xs4all.nl>, jan.kratochvil@redhat.com
Subject: Re: [patch] Forbid run with a core file loaded
Date: Fri, 21 May 2010 15:05:00 -0000 [thread overview]
Message-ID: <201005211605.01345.pedro@codesourcery.com> (raw)
In-Reply-To: <201005211447.o4LEl7tQ019880@glazunov.sibelius.xs4all.nl>
On Friday 21 May 2010 15:47:07, Mark Kettenis wrote:
> I often start gdb and load a core file to investigate a problem. Then
> I set a breakpoint at some point before the crash and run the program
> again. This used to work just fine.
If you're refering to getting back to debugging the core when
the running program exits, it never worked correctly. You'd get a better
experience if your core had no threads at all. If you didn't trip on an
assertion, and weird problems for having gdb consult things in the process
target, then the core target (which wouldn't make sense for the running
program), then the exec target, when you'd get back to debugging
the core, you'd find your threads had disapeared. That's just an example.
Here are others <http://sourceware.org/ml/gdb-patches/2008-08/msg00290.html>.
For this to work correctly, we'd need to rethink the single target-stack,
into maybe multiple target stacks, or something else radically different.
--
Pedro Alves
next prev parent reply other threads:[~2010-05-21 15:05 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-21 14:47 Jan Kratochvil
2010-05-21 15:02 ` Mark Kettenis
2010-05-21 15:05 ` Joel Brobecker
2010-05-21 15:40 ` Mark Kettenis
2010-05-23 19:38 ` Jan Kratochvil
2010-05-23 21:08 ` Eli Zaretskii
2010-06-06 19:51 ` Jan Kratochvil
2010-06-06 23:08 ` Eli Zaretskii
2010-06-07 11:21 ` Pedro Alves
2010-06-08 2:33 ` Tom Tromey
2010-06-08 11:03 ` Pedro Alves
2010-07-08 17:17 ` Jan Kratochvil
2010-07-08 18:28 ` Eli Zaretskii
2010-07-19 18:02 ` Jan Kratochvil
2010-07-19 18:05 ` Eli Zaretskii
2010-07-19 18:16 ` Jan Kratochvil
2010-07-27 16:00 ` Joel Brobecker
2010-07-19 14:37 ` Pedro Alves
2010-05-23 21:16 ` Pedro Alves
2010-05-21 15:05 ` Pedro Alves [this message]
2010-05-21 15:54 ` Mark Kettenis
2010-05-21 16:08 ` Pedro Alves
2010-05-21 15:07 ` Jan Kratochvil
2010-05-21 15:04 ` Joel Brobecker
2010-05-21 15:06 ` Pedro Alves
2010-05-21 15:15 ` 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=201005211605.01345.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=mark.kettenis@xs4all.nl \
/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).