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>,
	       Stan Shebs	<stan@codesourcery.com>,
	       "tromey@redhat.com" <tromey@redhat.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: RE: [PATCH] Print trace state variables
Date: Fri, 10 Dec 2010 16:35:00 -0000	[thread overview]
Message-ID: <F7CE05678329534C957159168FA70DEC572E0C0E10@EUSAACMS0703.eamcs.ericsson.se> (raw)
In-Reply-To: <20101210112600.GA2596@adacore.com>

From: Joel Brobecker [brobecker@adacore.com]

> > If this seems reasonable, I'll put in both trunk and 7.2 branch.
> 
> Is this the change that you were thinking we should wait for before
> releasing 7.2.1?
> 
> Tristan just informed me yesterday of another issue with etc/gnu-oids.texi
> missing, and I will backport his change in a second.  If all is ready and
> in, I should be able to make the release on, say, Monday.

Hi,

I was hoping to get the patch about the assertion failure when removing
an inferior into 7_2.  I believe Tom was ok with my solution, I'm just 
waiting for final approval.

http://sourceware.org/ml/gdb-patches/2010-12/msg00085.html

We actually hit this problem in Eclipse and GDB crashes when the user
tries to detach from a running process.  We could work around it if we
have to, but since I'm close to a fix for GDB, I was hoping to use
that solution with 7.2.1

Thanks

Marc


  parent reply	other threads:[~2010-12-10 16:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-09 22:38 Stan Shebs
2010-12-10 11:27 ` Joel Brobecker
2010-12-10 14:04   ` Stan Shebs
2010-12-10 16:35   ` Marc Khouzam [this message]
2010-12-10 20:00     ` Tom Tromey
2010-12-11  5:28       ` Joel Brobecker
2010-12-11  5:55 ` Joel Brobecker
2010-12-13  5:56   ` Stan Shebs
2010-12-13 13:00   ` Pedro Alves
2010-12-14 16:13   ` Tom Tromey
2010-12-13 12:31 ` Hui Zhu

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