Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: fche@redhat.com (Frank Ch. Eigler)
To: David Taylor <dtaylor@emc.com>
Cc: Yao Qi <yao@codesourcery.com>, "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: gdb remote protocol breakpoints (Z0 command)
Date: Tue, 24 Jun 2014 00:53:00 -0000	[thread overview]
Message-ID: <y0mha3b5dsn.fsf@fche.csb> (raw)
In-Reply-To: <2184.1403531084@usendtaylorx2l> (David Taylor's message of "Mon, 23 Jun 2014 09:44:44 -0400")


dtaylor wrote:

> [...]
> Both our old and our new stubs support tracepoints; our use of
> tracepoints preceeds GDB support for tracepoints.

I think I remember those early days.


> I've used it for things like setting a breakpoint on a
> troublesome functions and then creating a command list like --
>
>     print that the function was called and its arguments; for
>     structures, possibly print key elements of the structure
> [...]
>     print a backtrace
> [...]
>     set $retval = <current function>(<current arguments>)
> [...]

Uploading enough intelligence & information into the gdbstub
to perform inferior function calls, or especially backtraces,
is going to be a tough hill to climb.


>     re-enable breakpoint
>
> So, we end up with the function arguments, the return value, and
> selected other interesting information each time the function is called.

(Hey, you guys need to try out systemtap. :-)


- FChE


  reply	other threads:[~2014-06-24  0:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-19 14:44 David Taylor
2014-06-19 17:24 ` Tom Tromey
2014-06-23 13:14   ` David Taylor
2014-06-20  5:41 ` Yao Qi
2014-06-23 13:45   ` David Taylor
2014-06-24  0:53     ` Frank Ch. Eigler [this message]
2014-06-21  0:23 ` Frank Ch. Eigler
2014-06-23 13:29   ` David Taylor

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=y0mha3b5dsn.fsf@fche.csb \
    --to=fche@redhat.com \
    --cc=dtaylor@emc.com \
    --cc=gdb@sourceware.org \
    --cc=yao@codesourcery.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