From: Michael Eager <eager@eagerm.com>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: gdb-7.8 MIPS assert failure in findvar.c
Date: Fri, 27 Feb 2015 16:11:00 -0000 [thread overview]
Message-ID: <54F0972E.7070800@eagerm.com> (raw)
An assert failure on MIPS big-endian in findvar.c was fixed in
HEAD, but not applied to gdb-7.8.
The patch is here:
https://sourceware.org/ml/gdb-patches/2014-08/msg00567.html
Applied and tested on gdb-7.8. OK to apply to gdb-7.8-branch?
--
Michael Eager eager@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306 650-325-8077
next reply other threads:[~2015-02-27 16:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-27 16:11 Michael Eager [this message]
2015-03-02 14:29 ` Joel Brobecker
2015-03-02 17:59 ` Michael Eager
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=54F0972E.7070800@eagerm.com \
--to=eager@eagerm.com \
--cc=gdb-patches@sourceware.org \
/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