From: Jens-Christian Lache <lache@tu-harburg.de>
To: Nick Clifton <nickc@redhat.com>
Cc: gdb@sources.redhat.com
Subject: Re: [Fwd: a small bug in the arm simulator]
Date: Fri, 23 Feb 2001 11:59:00 -0000 [thread overview]
Message-ID: <0102232056240W.28931@lab04> (raw)
In-Reply-To: <p0ae7d4280.fsf@elmo.cygnus.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1773 bytes --]
(I wish...)
-------
I think it would be nice to have swi´s working properly. I don´t know
if this really belongs to a source level simulator or not.
Maybe it is not that much work to implement it. The different modes work
quite fine (more or less). I mentioned before that I can simulate swis and
interrupts manually. The simulator does provide the functionality already.
The steps I did to simulate a swi just have to be automated.
For hw interrupts could be applied the same. I can imagine an interrupt
button, which automatically executes the code from 0x18, set lr_irq and spsr.
That would be nice.
jc
Am Fre, 23 Feb 2001 schrieben Sie:
> Hi Jens-Christian,
>
> > Well, I could launch arm-elf-gdb from gdb, BUT just for a while.
> > At the moment gdb hangs when pressening the run button to start
> > arm-elf-gdb. This happens also for a helloWorld c-program.
>
> Oh dear :-(
>
> > The bug in the sim is still located in this snapshot.
> >
> > Unfortunatly, I am to clumsy at the std. gdb console (a stable version without
> > insight is installed an my system) That´s why I am compiling a different gdb
> > frontend called "ddd" which is hopefully a little more stable. Lesstif just
> > compiled fine and soon ddd will be compiled too (I hope). Unfortunately I don´t
> > have administrator right on my machine, that would make thinks faster.
>
> May I suggest an old fashioned approach to debugging - printf
> statements. This is how I debug the simulator. I add in fprintf(stderr,"...
> calls at the places I am interested in, recompile GDB and then run it.
>
> Cheers
> Nick
--
Jens-Christian Lache
Technische Universitaet Hamburg-Harburg
www.tu-harburg.de/~sejl1601
Mail:
lache@tu-harburg.de
lache@ngi.de
Tel.:
+0491759610756
next prev parent reply other threads:[~2001-02-23 11:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3A9686D2.CEEB419D@redhat.com>
2001-02-23 11:06 ` Nick Clifton
[not found] ` <0102232029510U.28931@lab04>
2001-02-23 11:38 ` Jens-Christian Lache
2001-02-23 12:15 ` Keith Seitz
2001-02-23 12:28 ` Jens-Christian Lache
2001-02-23 13:53 ` Jens-Christian Lache
[not found] ` <p0ae7d4280.fsf@elmo.cygnus.com>
2001-02-23 11:59 ` Jens-Christian Lache [this message]
2001-02-23 12:02 Jens-Christian Lache
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=0102232056240W.28931@lab04 \
--to=lache@tu-harburg.de \
--cc=gdb@sources.redhat.com \
--cc=nickc@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