This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: Set BP immediately
- From: "Krzysztof Blaszkowski" <info at sysmikro dot com dot pl>
- To: "Fabian Cenedese" <Cenedese at indel dot ch>
- Cc: <gdb at sources dot redhat dot com>
- Date: Thu, 12 Aug 2004 12:22:38 +0200
- Subject: Re: Set BP immediately
- References: <5.2.0.9.1.20040812111119.01d35768@NT_SERVER>
----- Original Message -----
From: "Fabian Cenedese" <Cenedese@indel.ch>
To: <gdb@sources.redhat.com>
Sent: Thursday, August 12, 2004 11:20 AM
Subject: Set BP immediately
> Hi
>
> I'm trying to debug an embedded PPC board with gdb, that's why I'm
> writing a stub. When I set a breakpoint in gdb (b file:nr), gdb just
records
> this internally and doesn't do anything with the target. Only upon step
> or cont it will set the breakpoint in the hardware. But we need the
> possibility to immediately set any breakpoint, even if it's for another
> not-halted thread. Is this possible with some gdb commands (like
> set PC) or would I need to change the code (break flush :) .. ok, better
> name it break apply... or set break apply 1) ?
You could use a "monitor" command (abbrev. "mo") with an argument list any
kind you wish for that purpose I think.
You can see also a spec. for mine arm7tdmi jtag debugger which is available
here: http://www.sysmikro.com.pl/pliki/jtag-adapterII_um.pdf
>
> Thanks
>
> bye Fabi
>
>
>
Best regards,
Krzysztof Blaszkowski