Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Marc Khouzam <marc.khouzam@ericsson.com>
To: "'Joel Brobecker'" <brobecker@adacore.com>,
	       "'Tom Tromey'" <tromey@redhat.com>
Cc: "'gdb-patches@sourceware.org'" <gdb-patches@sourceware.org>
Subject: RE: Assertion failure because of missing inferior
Date: Tue, 14 Dec 2010 20:00:00 -0000	[thread overview]
Message-ID: <F7CE05678329534C957159168FA70DEC572E9D937F@EUSAACMS0703.eamcs.ericsson.se> (raw)
In-Reply-To: <20101214150430.GV2596@adacore.com>

> -----Original Message-----
> From: gdb-patches-owner@sourceware.org 
> [mailto:gdb-patches-owner@sourceware.org] On Behalf Of Joel Brobecker
> Sent: Tuesday, December 14, 2010 10:05 AM
> To: Tom Tromey
> Cc: Marc Khouzam; gdb-patches@sourceware.org
> Subject: Re: Assertion failure because of missing inferior
> 
> > Marc> 2010-12-10  Marc Khouzam  <marc.khouzam@ericsson.com>
> > Marc>    * mi/mi-main.c (mi_cmd_remove_inferior): Don't 
> delete current inferior.
> > Marc>    (get_other_inferior): New.
> > 
> > I think this is ok for the 7.2 branch, assuming Joel didn't do the
> > release already :)
> 
> I'll wait for the go ahead from you guys - I get confused with the
> various emails...

So, although I feel that this patch is good, it seems to be
only a first step in getting 'remove-inferior' to work.  Once
I have this patch applied, I'm getting further but hitting
another crash.  I'm still working on a patch for that.  I don't
think the current patch is going to help 7.2.1 unless the other
crash is also fixed, so I'll wait before committing it.

I guess I have just a little more time, until the issue below 
(watchpoint-related patch) is ready, to try to fix the latest
crash.  I'll do my best.

Thanks

Marc

> There is also a watchpoint-related patch (from Pedro) which 
> Jan pointed
> out.  It looks a little riskier than the typical patch, but it fixes
> crashes and has been in HEAD for 4 months now.  So I suggested the
> possibility of maybe putting it in, if we don't know of any issue that
> this patch caused since putting it in HEAD....
> 
> -- 
> Joel
> 


  parent reply	other threads:[~2010-12-14 20:00 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-04 19:11 Marc Khouzam
2010-12-07 18:54 ` Tom Tromey
2010-12-08  1:38   ` Marc Khouzam
2010-12-10 19:59     ` Tom Tromey
2010-12-10 20:21       ` Marc Khouzam
2010-12-10 21:01         ` Marc Khouzam
2010-12-10 21:38           ` Marc Khouzam
2010-12-14 14:50             ` Tom Tromey
2010-12-14 15:04               ` Joel Brobecker
2010-12-14 15:31                 ` Pedro Alves
2010-12-15  5:12                   ` Joel Brobecker
2010-12-14 20:00                 ` Marc Khouzam [this message]
2010-12-15 15:57                   ` [Python] Segfault when clearing pspace (was: RE: Assertion failure because of missing inferior) Marc Khouzam
2010-12-16 21:26                     ` [Python] Segfault when clearing pspace Tom Tromey
2010-12-18  2:13                       ` Marc Khouzam
2010-12-18  2:19               ` Assertion failure because of missing inferior Marc Khouzam
2010-12-14 14:49           ` Tom Tromey

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=F7CE05678329534C957159168FA70DEC572E9D937F@EUSAACMS0703.eamcs.ericsson.se \
    --to=marc.khouzam@ericsson.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --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