From: Daniel Jacobowitz <drow@false.org>
To: Markus Deuling <deuling@de.ibm.com>
Cc: GDB Patches <gdb-patches@sourceware.org>
Subject: Re: Bug in mips:3900 arch ?
Date: Thu, 31 Jan 2008 22:35:00 -0000 [thread overview]
Message-ID: <20080131222104.GC6715@caradoc.them.org> (raw)
In-Reply-To: <479DEAAA.4050108@de.ibm.com>
On Mon, Jan 28, 2008 at 03:46:02PM +0100, Markus Deuling wrote:
> Hi,
>
> I'm currently writing a little helper script a la gdb_mbuild.sh to cover
> the new "--enable-targets-all" flag and I think I found a bug.
>
> This GDB was configured as "i686-pc-linux-gnu".
> (gdb) set architecture mips:3900
> /home/deuling/gdb/dev/gdb/mips-linux-tdep.c:1152: internal-error: can't handle ABI
> A problem internal to GDB has been detected,
> further debugging may prove unreliable.
> Quit this debugging session? (y or n)
>
> "mips:3900" is one of the possible target architectures given by GDB when invoking "set architecture" without a parameter.
> Shouldn't this work? For my opinion it should always be possible to switch to one of these archs without crashing.
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.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-01-31 22:21 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 [this message]
2008-02-14 6:14 ` Markus Deuling
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=20080131222104.GC6715@caradoc.them.org \
--to=drow@false.org \
--cc=deuling@de.ibm.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