From: Janne Hellsten <jjhellst@gmail.com>
To: gdb@sources.redhat.com
Subject: Re: two bugs in the arm simulator
Date: Tue, 05 Jul 2005 08:01:00 -0000 [thread overview]
Message-ID: <700d600f05070501016d51ea6c@mail.gmail.com> (raw)
In-Reply-To: <700d600f050703200612732a64@mail.gmail.com>
Hi,
> I have submitted two bug reports to the GDB bug database (PR #1957 and
> PR #1900). Both of these are issues in the ARM simulator.
Looks like PR 1957 is already fixed in CVS. I tested compiling both
gdb-6.3 and the CVS with GCC 4.0.0, and while the 6.3 version didn't
compile, the CVS version did.
As a work-around for PR 1900, I guess I could compile GDB into a
32-bit binary (on an x86_64 host). Is this somehow possible?
Best regards,
Janne
next prev parent reply other threads:[~2005-07-05 8:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-04 3:06 Janne Hellsten
2005-07-04 3:56 ` Daniel Jacobowitz
2005-07-04 6:20 ` Janne Hellsten
2005-07-04 15:28 ` Daniel Jacobowitz
2005-07-05 0:07 ` number of executed instructions from simulator (was Re: two bugs in the arm simulator) Janne Hellsten
2005-07-05 8:01 ` Janne Hellsten [this message]
2005-07-05 13:29 ` two bugs in the arm simulator Daniel Jacobowitz
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=700d600f05070501016d51ea6c@mail.gmail.com \
--to=jjhellst@gmail.com \
--cc=gdb@sources.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