Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Orjan Friberg <orjan.friberg@axis.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: Next over function and breakpoint setting
Date: Mon, 29 Mar 2004 08:48:00 -0000	[thread overview]
Message-ID: <4067E2A8.7040307@axis.com> (raw)
In-Reply-To: <20040327055037.GA9418@nevyn.them.org>

Daniel Jacobowitz wrote:
> 
> "The next line of code" is a very iffy concept.  GDB doesn't analyze a
> line to figure out what it does, or where it might transfer control
> to... while possible, that would be a very different approach to
> debugging.  So the only way we have to implement next is to step and
> see where we end up - and if we don't like it, go until we're somewhere
> else.

I guess I wasn't really asking a question - I was just confused by the 
way it was implemented since it wasn't what I had expected.  Anyhow, 
thanks for clearing that up.

-- 
Orjan Friberg
Axis Communications


  reply	other threads:[~2004-03-29  8:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-19  0:09 Orjan Friberg
2004-03-16 15:42 ` Orjan Friberg
2004-03-27  5:50 ` Daniel Jacobowitz
2004-03-29  8:48   ` Orjan Friberg [this message]
2004-03-29 13:36     ` Andrew Cagney

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=4067E2A8.7040307@axis.com \
    --to=orjan.friberg@axis.com \
    --cc=drow@false.org \
    --cc=gdb-patches@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