This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: set breakpoints in remote debugging
- From: Daniel Jacobowitz <drow at false dot org>
- To: fzchuan <fzchuan at eos dot cs dot nthu dot edu dot tw>
- Cc: gdb at sourceware dot org
- Date: Wed, 2 Nov 2005 12:36:19 -0500
- Subject: Re: set breakpoints in remote debugging
- References: <20051102171409.M10763@eos.cs.nthu.edu.tw> <20051102173427.M31340@eos.cs.nthu.edu.tw>
On Thu, Nov 03, 2005 at 01:34:48AM +0800, fzchuan wrote:
>
> Hi all:
>
> I encountered some problems in GDB remote debugging.
> In most of time, GDB host would send correct breakpoint address to target which
> I asked it. But sometimes it would send strange address.
> That is,in GDB host side,I set breakpoint on some address,i.e.:
> (gdb)b *0x8
>
> Then, in target side, target will receive the request.
> I print the message received from GDB host,
> and it shows that GDB ask target to stop at 0xc6
>
> I use GDB disassemble to query 0x8, and is shows that it is a Call (JUMP)
> instruction and jump target address is 0xc6.
>
> Why? thanks
There is not enough information to answer your question. When does
this happen? What does the remote protocol and GDB console show when
it does? What target is this?
--
Daniel Jacobowitz
CodeSourcery, LLC