From: Andrew Cagney <cagney@gnu.org>
To: Orjan Friberg <orjan.friberg@axis.com>
Cc: Daniel Jacobowitz <drow@false.org>, gdb-patches@sources.redhat.com
Subject: Re: Next over function and breakpoint setting
Date: Mon, 29 Mar 2004 13:36:00 -0000 [thread overview]
Message-ID: <40682659.5060304@gnu.org> (raw)
In-Reply-To: <4067E2A8.7040307@axis.com>
> 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.
BTW, have a look at the step out of range code. The theory is that the
target be presented with a range of addresses and it run until it leave
that range (as is the case with a step or next).
The implementation breaks the theory -- the code didn't consider threads
and multi-threaded interactions. As far as I'm concerned, to fix the
theory we need to disentangle threads.
Andrew
prev parent reply other threads:[~2004-03-29 13:36 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
2004-03-29 13:36 ` Andrew Cagney [this message]
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=40682659.5060304@gnu.org \
--to=cagney@gnu.org \
--cc=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=orjan.friberg@axis.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