From: Luis Machado <lgustavo@codesourcery.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [obv] [testsuite] i386-biarch-core.exp: Fix comment typo
Date: Tue, 15 Sep 2015 14:51:00 -0000 [thread overview]
Message-ID: <55F83064.5020501@codesourcery.com> (raw)
In-Reply-To: <20150915143720.GA23411@host1.jankratochvil.net>
On 09/15/2015 11:37 AM, Jan Kratochvil wrote:
> On Tue, 15 Sep 2015 16:35:28 +0200, Luis Machado wrote:
>> On 09/15/2015 11:29 AM, Luis Machado wrote:
>>> core-file gdb.arch/i386-biarch-core.core
>>> gdb/mips-tdep.c:1098: internal-error: bad register size
>>> A problem internal to GDB has been detected,
>>> further debugging may prove unreliable.^
>>> Quit this debugging session? (y or n)
>>> FAIL: gdb.arch/i386-biarch-core.exp: core-file (GDB internal error)
>>
>> The lines are a bit off, but basically we end up hitting the internal error
>> at mips-tdep.c:mips_pseudo_register_read. I don't think the MIPS backend is
>> currently crafted to handle reading unknown register blocks.
>
> Then it is a mips-tdep.c bug similar to this i386-tdep.c bug:
> https://sourceware.org/bugzilla/show_bug.cgi?id=17808
>
> In general GDB should not crash when you let it read an arbitrary file.
>
> If you want I can file it as a new MIPS-specific PR and KFAIL it.
Yes, thanks. That would be helpful. No need to KFAIL it though. It
should be fixed soon.
next prev parent reply other threads:[~2015-09-15 14:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-14 17:51 Jan Kratochvil
2015-09-15 14:03 ` Luis Machado
2015-09-15 14:22 ` Jan Kratochvil
2015-09-15 14:30 ` Luis Machado
2015-09-15 14:35 ` Luis Machado
2015-09-15 14:37 ` Jan Kratochvil
2015-09-15 14:51 ` Luis Machado [this message]
2015-09-15 14:58 ` Jan Kratochvil
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=55F83064.5020501@codesourcery.com \
--to=lgustavo@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@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