This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
re: gdb breakpoint
- From: "Yorkwar" <yorkwar at xinhuanet dot com>
- To: "vineets" <vineets at noida dot hcltech dot com>
- Cc: "gdb" <gdb at sources dot redhat dot com>
- Date: Fri, 5 Mar 2004 09:33:49 +0800
- Subject: re: gdb breakpoint
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:)