From: "Modi Banti" <b.modi@sssup.it>
To: gdb@sources.redhat.com
Subject: Remote stub for ARM processor
Date: Sun, 27 Jun 2004 02:26:00 -0000 [thread overview]
Message-ID: <web-4609543@sssup.it> (raw)
Hi,
I am trying to buikd a remote stub for an ARM processor
Simulator. I have couple of problems with this...
1) When a Simulator arrives at a breakpoint it sends the
signal SIGTRAP 15 (register number): PC to GDB so the GDB
stops and shows the instruction at PC but since for ARM
processor PC point to current instruction + 8, so it shows
me a wrong line. I am not sure while displaying the line
GDB takes into account of Pipiline. I can overcome this
problem tempararily by sending the signal SIGTRAP 15: PC-
8. so it works correctly but I am not sure if this is the
correct way of doing it.
2) In reply to GDBs $s#73 (single step) command i send the
same packet i.e SIGTRAP 15: PC - 8 . I am not sure if I
need to send SIGTRAP or some other signal. Here also the
'n' command works prefectly fine with normal code but if
it is a Function call then instead of stopping at next
line GDB stops at line after that
e. g for following code
Mutex_lock(&mut);
++i;
++j;
if I give 'n' command when GDB is at Mutex_lock(&mut)
then it gives some series of $s#73 commands and finaly
stops at ++j instead of stopping at ++i. this happens only
in case of function call for normal statements it works
perfectly fine. Here I am not sure whether SIGTRAP is a
right signal and secondly sending PC -15 is correct or not
( if i send just PC here then insted og going to next
instruction GDB steps in the function call).
Can anybody help me with this or tell me which part of
code in GDB handles this step instruction?
Thanks and regards,
Banti
next reply other threads:[~2004-06-27 2:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-27 2:26 Modi Banti [this message]
2004-06-27 23:50 ` Steven Johnson
2004-06-28 14:03 ` Modi Banti
2004-07-10 16:11 ` How does GDB informs remote stub about '^Cremote_interrupt called ' Modi Banti
2004-07-11 5:32 ` Alexander Stante
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=web-4609543@sssup.it \
--to=b.modi@sssup.it \
--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