From: Marc Khouzam <marc.khouzam@ericsson.com>
To: "'Pedro Alves'" <pedro@codesourcery.com>,
"'gdb-patches@sourceware.org'"
<gdb-patches@sourceware.org>
Cc: "'Tom Tromey'" <tromey@redhat.com>
Subject: RE: segfault: what should happen when I remove an inferior that is running?
Date: Wed, 22 Dec 2010 22:02:00 -0000 [thread overview]
Message-ID: <F7CE05678329534C957159168FA70DEC5730924C5E@EUSAACMS0703.eamcs.ericsson.se> (raw)
In-Reply-To: <201012221817.17271.pedro@codesourcery.com>
> -----Original Message-----
> From: Pedro Alves [mailto:pedro@codesourcery.com]
> Sent: Wednesday, December 22, 2010 1:17 PM
> To: gdb-patches@sourceware.org
> Cc: Marc Khouzam; 'Tom Tromey'
> Subject: Re: segfault: what should happen when I remove an
> inferior that is running?
>
> On Wednesday 22 December 2010 18:11:45, Marc Khouzam wrote:
> > > > If it is ok, please let me know if you want it only in HEAD or
> > > > also in 7_2.
> > >
> > > "running inferior" will sound a bit odd for cores, but,
> > > since I don't have a better suggestion that wouldn't involve
> > > more coding, this is okay with me (HEAD and 7_2).
> >
> > Would "Can not remove a an active inferior." be better?
>
> Fine with me.
I committed the following to 7_2 and HEAD.
Thanks
Marc
2010-12-22 Marc Khouzam <marc.khouzam@ericsson.com>
* inferior.c (remove_inferior_command): Don't remove an active inferior.
* mi/mi-main.c (mi_cmd_remove_inferior): Ditto.
### Eclipse Workspace Patch 1.0
#P src
Index: gdb/inferior.c
===================================================================
RCS file: /cvs/src/src/gdb/inferior.c,v
retrieving revision 1.18
diff -u -r1.18 inferior.c
--- gdb/inferior.c 14 May 2010 21:25:51 -0000 1.18
+++ gdb/inferior.c 22 Dec 2010 18:18:55 -0000
@@ -741,6 +741,9 @@
if (inf == current_inferior ())
error (_("Can not remove current symbol inferior."));
+
+ if (inf->pid != 0)
+ error (_("Can not remove an active inferior."));
delete_inferior_1 (inf, 1);
}
Index: gdb/mi/mi-main.c
===================================================================
RCS file: /cvs/src/src/gdb/mi/mi-main.c,v
retrieving revision 1.178.2.5
diff -u -r1.178.2.5 mi-main.c
--- gdb/mi/mi-main.c 18 Dec 2010 01:56:07 -0000 1.178.2.5
+++ gdb/mi/mi-main.c 22 Dec 2010 18:18:55 -0000
@@ -1651,6 +1651,9 @@
if (!inf)
error ("the specified thread group does not exist");
+ if (inf->pid != 0)
+ error ("can not remove an active inferior");
+
if (inf == current_inferior ())
{
struct thread_info *tp = 0;
next prev parent reply other threads:[~2010-12-22 18:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <F7CE05678329534C957159168FA70DEC572E0C0E1A@EUSAACMS0703.eamcs.ericsson.se>
[not found] ` <m3oc8otms0.fsf@fleche.redhat.com>
[not found] ` <201012141523.51109.pedro@codesourcery.com>
2010-12-18 2:47 ` Marc Khouzam
2010-12-22 12:10 ` Pedro Alves
2010-12-22 18:32 ` Marc Khouzam
2010-12-22 18:45 ` Pedro Alves
2010-12-22 22:02 ` Marc Khouzam [this message]
2010-12-23 4:02 ` Joel Brobecker
2010-12-23 5:27 ` Joel Brobecker
2011-01-06 18:57 ` Marc Khouzam
2011-01-06 20:17 ` Tom Tromey
2011-01-06 20:37 ` 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=F7CE05678329534C957159168FA70DEC5730924C5E@EUSAACMS0703.eamcs.ericsson.se \
--to=marc.khouzam@ericsson.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.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