From: Tom Tromey <tromey@redhat.com>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: RFC: fix PR gdb/15538
Date: Tue, 16 Apr 2013 07:52:00 -0000 [thread overview]
Message-ID: <87haj7bmgd.fsf@fleche.redhat.com> (raw)
In-Reply-To: <516C5988.8070507@redhat.com> (Pedro Alves's message of "Mon, 15 Apr 2013 20:48:24 +0100")
>>>>> "Pedro" == Pedro Alves <palves@redhat.com> writes:
Pedro> Bugzilla says 15538 does not exist.
Transcription error, it is
http://sourceware.org/bugzilla/show_bug.cgi?id=15338
>> The bug is that dwarf2_record_block_ranges asserts that the ranges
>> section has been read in -- but it can be called without this occurring.
Pedro> Can you show the backtrace for the archives?
There isn't one, but I can ask the reporter for it.
I didn't ask earlier since I thought the problem was obvious from the
assertion failure.
Tom
next prev parent reply other threads:[~2013-04-15 19:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-16 5:54 Tom Tromey
2013-04-16 7:52 ` Pedro Alves
2013-04-16 7:52 ` Tom Tromey [this message]
2013-04-16 15:45 ` Tom Tromey
2013-05-13 16:54 ` 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=87haj7bmgd.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@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