Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: Jim Ingham <jingham@apple.com>, gdb@sources.redhat.com
Subject: Re: gdb Digest 26 Mar 2003 19:03:48 -0000 Issue 1129
Date: Sat, 29 Mar 2003 01:32:00 -0000	[thread overview]
Message-ID: <3E84F7BB.3040908@redhat.com> (raw)
In-Reply-To: <20030329005823.GA7072@nevyn.them.org>

> 
> OK, two levels.  We still need to think about the interface for the top
> level though.  You want to be able to specify the set in some way...

yes.

> This sort of design is not my strong point.
> 
> 
>> >Does anyone know how other debuggers handle this?  I'm sure we're not
>> >the first but it's been ages since I used a non-GDB debugger for
>> >anything.
> 
>> 
>> The model I'm describing lifted from a book, the author of which was 
>> involved in borland's debugger.
> 
> 
> Yes, I've heard of the book.  Does it cover things like inlined
> functions?

It does, but it `paints with a broad brush'.  Don't expect a technical 
cook book.  Rather something that sets a good direction and identifies 
the basic issues.

I think you already know: breakpoint on an in-line function means 
finding all instances and then adding a physical breakpoint for each.

Andrew



  reply	other threads:[~2003-03-29  1:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1048705428.15342.ezmlm@sources.redhat.com>
2003-03-26 19:37 ` Jim Ingham
2003-03-28 22:49   ` Andrew Cagney
2003-03-28 23:13     ` Andrew Cagney
2003-03-28 23:56       ` Daniel Jacobowitz
2003-03-29  0:49         ` Andrew Cagney
2003-03-29  0:58           ` Daniel Jacobowitz
2003-03-29  1:32             ` Andrew Cagney [this message]
2003-03-29  3:30             ` Jim Ingham

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=3E84F7BB.3040908@redhat.com \
    --to=ac131313@redhat.com \
    --cc=drow@mvista.com \
    --cc=gdb@sources.redhat.com \
    --cc=jingham@apple.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