From: Tom Tromey <tromey@redhat.com>
To: Marc Khouzam <marc.khouzam@ericsson.com>
Cc: "gdb\@sourceware.org" <gdb@sourceware.org>,
"pedro\@codesourcery.com" <pedro@codesourcery.com>
Subject: Re: segfault: what should happen when I remove an inferior that is running?
Date: Tue, 14 Dec 2010 15:08:00 -0000 [thread overview]
Message-ID: <m3oc8otms0.fsf@fleche.redhat.com> (raw)
In-Reply-To: <F7CE05678329534C957159168FA70DEC572E0C0E1A@EUSAACMS0703.eamcs.ericsson.se> (Marc Khouzam's message of "Fri, 10 Dec 2010 16:22:47 -0500")
>>>>> "Marc" == Marc Khouzam <marc.khouzam@ericsson.com> writes:
Marc> I gather removing a running inferior is not a good idea, but
Marc> I think we should protect GDB against that user mistake
Marc> somehow.
I agree.
Thanks for the simple example. I was able to reproduce it here.
Marc> Any suggestions on how to handle this case?
The docs say:
Removes the inferior INFNO. It is not possible to remove an
inferior that is running with this command.
I think this means we are missing an error check somewhere.
Tom
next prev parent reply other threads:[~2010-12-14 15:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-10 21:24 Marc Khouzam
2010-12-14 15:08 ` Tom Tromey [this message]
2010-12-14 15:24 ` Pedro Alves
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=m3oc8otms0.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb@sourceware.org \
--cc=marc.khouzam@ericsson.com \
--cc=pedro@codesourcery.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