From: Tom Tromey <tromey@redhat.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb@sourceware.org, Kai Tietz <ktietz70@googlemail.com>,
Chris Sutcliffe <ir0nh34d@gmail.com>
Subject: Re: [gdb-7.1] 10 days to branching...
Date: Thu, 11 Feb 2010 18:25:00 -0000 [thread overview]
Message-ID: <m3eikrsk8p.fsf@fleche.redhat.com> (raw)
In-Reply-To: <201002061626.06963.pedro@codesourcery.com> (Pedro Alves's message of "Sat, 6 Feb 2010 16:26:06 +0000")
>>>>> "Pedro" == Pedro Alves <pedro@codesourcery.com> writes:
[ gdb crasher ]
Pedro> This one's been described and diagnosed in
Pedro> PR10966 <http://sourceware.org/bugzilla/show_bug.cgi?id=10966>
Pedro> The expr-cumulative work fixes this, but I listed in the PR
Pedro> two possible quick workarounds.
It may go without saying, but I think we should apply one of the
workarounds to the 7.1 branch, once it is made.
I'll add a note to the 7.1 wiki page.
Tom
next prev parent reply other threads:[~2010-02-11 18:25 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-01 8:20 Joel Brobecker
2010-02-01 16:09 ` Chris Sutcliffe
2010-02-02 4:17 ` Joel Brobecker
2010-02-02 12:35 ` Chris Sutcliffe
2010-02-02 16:02 ` Kai Tietz
2010-02-02 16:27 ` Christopher Faylor
2010-02-02 16:46 ` Chris Sutcliffe
2010-02-02 18:46 ` Kai Tietz
2010-02-02 22:44 ` Christopher Faylor
2010-02-03 8:20 ` Kai Tietz
2010-02-03 19:39 ` Christopher Faylor
2010-02-05 22:02 ` Tom Tromey
2010-02-06 4:55 ` Joel Brobecker
2010-02-06 16:26 ` Pedro Alves
2010-02-06 18:41 ` Matt Rice
2010-02-11 18:25 ` Tom Tromey [this message]
[not found] ` <20100212051007.GI2919@adacore.com>
2010-02-12 6:16 ` Joel Brobecker
2010-02-12 11:37 ` Pedro Alves
2010-02-12 11:47 ` Pedro Alves
2010-02-12 17:13 ` Tom Tromey
2010-02-12 19:01 ` Pedro Alves
2010-02-12 20:11 ` Michael Snyder
2010-02-03 8:15 ` André Pönitz
2010-02-03 12:01 ` Chris Sutcliffe
2010-02-12 1:24 ` Stan Shebs
2010-02-12 5:11 ` Joel Brobecker
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=m3eikrsk8p.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb@sourceware.org \
--cc=ir0nh34d@gmail.com \
--cc=ktietz70@googlemail.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