From: "Yorkwar" <yorkwar@xinhuanet.com>
To: "vineets" <vineets@noida.hcltech.com>
Cc: "gdb" <gdb@sources.redhat.com>
Subject: re: gdb breakpoint
Date: Fri, 05 Mar 2004 01:34:00 -0000 [thread overview]
Message-ID: <M6959694906274.00630@mailcom1> (raw)
Usually gdb together with the simulator is a single thread.
GDB sees the integrated simulator as a set of functions.
If you set a breakpoint in gdb, gdb will replace the appropriate
instruction with some "break number"-like instruction and rember
the original instruction. When the simulator meets with the gdb-
inserted break instruction, it will return the control to gdb's
main loop.
Everytime gdb transfers it's control to simulator, it invokes
sim_resume.
That's my opinion:)
next reply other threads:[~2004-03-05 1:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-05 1:34 Yorkwar [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-03-04 14:51 Vineet Sharma, Noida
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=M6959694906274.00630@mailcom1 \
--to=yorkwar@xinhuanet.com \
--cc=gdb@sources.redhat.com \
--cc=vineets@noida.hcltech.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