From: Tom Tromey <tromey@redhat.com>
To: nickrob@snap.net.nz (Nick Roberts)
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] PR backtrace/9786
Date: Mon, 20 Apr 2009 17:19:00 -0000 [thread overview]
Message-ID: <m3k55f450c.fsf@fleche.redhat.com> (raw)
In-Reply-To: <18921.8753.647539.260364@totara.tehura.co.nz> (Nick Roberts's message of "Sat\, 18 Apr 2009 12\:43\:29 +1200")
>>>>> "Nick" == Nick Roberts <nickrob@snap.net.nz> writes:
Nick> Current behaviour breaks remote debugging when using GDB in Emacs as it
Nick> currently uses "info frame". If this behaviour can't be fully resolved
Nick> before the release could a less than perfect patch be applied to prevent
Nick> the assertion error?
I don't know anything about this patch, so I can't really answer
that... but could you add this to the wiki as a release blocker?
I think that's the best way to ensure that some decision is made
before 7.0.
Tom
next prev parent reply other threads:[~2009-04-20 17:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-22 19:37 Nick Roberts
2009-02-23 0:51 ` Joel Brobecker
2009-02-23 1:08 ` Pedro Alves
2009-02-23 2:08 ` Daniel Jacobowitz
2009-04-18 0:43 ` Nick Roberts
2009-04-20 17:19 ` Tom Tromey [this message]
2009-04-21 8:28 ` Nick Roberts
2009-06-23 18:39 ` Joel Brobecker
2009-06-23 18:46 ` Daniel Jacobowitz
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=m3k55f450c.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=nickrob@snap.net.nz \
/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