From: Andrew Cagney <ac131313@cygnus.com>
To: Mattias Wildeman <wilde@acc.com>
Cc: gdb@sources.redhat.com
Subject: Re: Nonblocking GDB stub
Date: Sun, 03 Mar 2002 09:03:00 -0000 [thread overview]
Message-ID: <3C8256F2.9000704@cygnus.com> (raw)
In-Reply-To: <3C80203E.49EFDC35@acc.com>
> Hello!
>
> I've been using GDB for a while, running it with a ARM based board and a
>
> serial connection (remote debugging).
>
> To activate GDB, i'll install a breakpoint on the target and connect GDB
> throught that.
> Standard behavior.
>
> Now, what i would like to do is to have GDB interact with the target
> without the target being stopped.
> Yes, this breaks some of the purpose of the debugger, but i would like
> to use GDB to analyze memory and datastructures without freezing the
> program. The OS i am running do support task-switching, so i was
> thinking about making the stub exception_handler non-blocking (e.g.
> remove the while(1==1) statement that makes it accept commands until i
> kill it), and instead have a call scheduled for it regularly.
>
> Has anyone had experience with doing this? Or know of any place were i
> could get more information on this? Is it even feasible?
>
> I looked through Google, but was unable to find anything on this level.
>
> Thank you for your time!
Perhaphs have a look through the tracepoints section of the documentation:
http://sources.redhat.com/gdb/onlinedocs/gdb_10.html#SEC68
Another option is to look at modifying GDB so that it doesn't stop all
threads - instead only specified threads. This is a little bit more
ambitious though.
Andrew
next prev parent reply other threads:[~2002-03-03 17:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-01 16:42 Mattias Wildeman
2002-03-03 9:03 ` Andrew Cagney [this message]
2002-03-05 21:15 ` Michael Snyder
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=3C8256F2.9000704@cygnus.com \
--to=ac131313@cygnus.com \
--cc=gdb@sources.redhat.com \
--cc=wilde@acc.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