public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Fabian Cenedese <Cenedese@indel.ch>
To: <gdb@sources.redhat.com>
Subject: Re: Set BP immediately
Date: Thu, 12 Aug 2004 10:52:00 -0000	[thread overview]
Message-ID: <5.2.0.9.1.20040812124541.01d39a40@NT_SERVER> (raw)
In-Reply-To: <000601c48056$4b741ca0$20ffffc0@sysc1300>


>> 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.

That's really useful to know. Funny that I couldn't find anything in the whole
gdb manual about it (from 20040728). Is this also in the MI? I couldn't find
a single hint.

>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

Nice document, seems like you're already on it for some time :) At the
moment we create a "normal" debugger, but eventually a jtag debugger
could also be made. I'll sure read this, thanks for the link.

bye  Fabi


  reply	other threads:[~2004-08-12 10:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-12  9:20 Fabian Cenedese
2004-08-12 10:27 ` Krzysztof Blaszkowski
2004-08-12 10:52   ` Fabian Cenedese [this message]
2004-08-12 12:25   ` Madhvesh R S

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=5.2.0.9.1.20040812124541.01d39a40@NT_SERVER \
    --to=cenedese@indel.ch \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).