From: Markus Deuling <deuling@de.ibm.com>
To: Daniel Jacobowitz <drow@false.org>,
GDB Patches <gdb-patches@sourceware.org>
Subject: Re: Bug in mips:3900 arch ?
Date: Thu, 14 Feb 2008 06:14:00 -0000 [thread overview]
Message-ID: <47B3DB9E.1050100@de.ibm.com> (raw)
In-Reply-To: <20080131222104.GC6715@caradoc.them.org>
[-- Attachment #1: Type: text/plain, Size: 843 bytes --]
Hi Daniel,
Daniel Jacobowitz schrieb:
> On Mon, Jan 28, 2008 at 03:46:02PM +0100, Markus Deuling wrote:
> Yes, this looks like a bug. It is caused by the special case in
> mips_gdbarch_init, by the comment:
>
> /* Try the architecture for any hint of the correct ABI. */
>
> I think replacing the internal error by "return" or "break" would be
> safe. No real Linux application will ever have the EABI32 or EABI64
> ABIs.
sorry for the late response. This patch simply removes the internal error. Maybe it would be a
good idea to add a warning instead? But as you say no Linux application will ever run into this
so the warning might be unnecessary.
Is this patch ok?
ChangeLog:
* mips-linux-tdep.c (mips_linux_init_abi): Remove internal error.
--
Markus Deuling
GNU Toolchain for Linux on Cell BE
deuling@de.ibm.com
[-- Attachment #2: fix-mips --]
[-- Type: text/plain, Size: 434 bytes --]
diff -urpN src/gdb/mips-linux-tdep.c dev/gdb/mips-linux-tdep.c
--- src/gdb/mips-linux-tdep.c 2008-01-01 23:53:12.000000000 +0100
+++ dev/gdb/mips-linux-tdep.c 2008-02-14 06:54:39.000000000 +0100
@@ -1149,7 +1149,6 @@ mips_linux_init_abi (struct gdbarch_info
tramp_frame_prepend_unwinder (gdbarch, &mips_linux_n64_rt_sigframe);
break;
default:
- internal_error (__FILE__, __LINE__, _("can't handle ABI"));
break;
}
next prev parent reply other threads:[~2008-02-14 6:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-28 15:48 Markus Deuling
2008-01-31 22:35 ` Daniel Jacobowitz
2008-02-14 6:14 ` Markus Deuling [this message]
2008-02-14 17:12 ` Daniel Jacobowitz
2008-02-15 4:52 ` Markus Deuling
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=47B3DB9E.1050100@de.ibm.com \
--to=deuling@de.ibm.com \
--cc=drow@false.org \
--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