Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@codesourcery.com>
To: Frederic RISS <frederic.riss@st.com>
Cc: "Daniel Jacobowitz" <drow@false.org>,
	"Frédéric Riss" <frederic.riss@gmail.com>,
	"Vladimir Prus" <ghost@cs.msu.su>,
	gdb-patches@sources.redhat.com
Subject: Re: [RFC] Prints the frame id when target stops
Date: Thu, 18 Jan 2007 18:34:00 -0000	[thread overview]
Message-ID: <m33b68b2v4.fsf@codesourcery.com> (raw)
In-Reply-To: <1169107060.3288.126.camel@localhost.localdomain> (Frederic RISS's message of "Thu, 18 Jan 2007 08:57:40 +0100")


Frederic RISS <frederic.riss@st.com> writes:
>> I suspect you can only do this in stepi, really - step/next can end up
>> in strange places...
>
> ... and end up in a frame with the same frame id? Seems unlikely, but
> then GDB isn't the place where you'd want to trade accuracy for a very
> small speedup.

Yeah --- I'd be very concerned about GDB performance optimizations
that would cause GDB to not notice, say, corruptions of the stack by
buffer overruns.

If it's common for memory reads to be so expensive, you should buy a
better JTAG unit^W^W^W^W^W^W^W I'd rather we work on minimizing memory
accesses by unwinders than make assumptions which may not hold in
buggy programs.

Could you enable 'debug remote' while it's doing the unwinding, and
figure out what it's actually fetching?


  reply	other threads:[~2007-01-18 18:34 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-15 16:21 Denis PILAT
2007-01-15 21:37 ` Nick Roberts
2007-01-15 23:11   ` Nick Roberts
2007-01-15 23:49     ` Nick Roberts
2007-01-17  8:26       ` Denis PILAT
2007-01-16 16:20 ` Vladimir Prus
2007-01-16 21:12   ` Nick Roberts
2007-01-16 23:38     ` Vladimir Prus
2007-01-17  6:18       ` Daniel Jacobowitz
2007-01-17 21:46         ` Vladimir Prus
2007-01-20 17:02           ` Daniel Jacobowitz
2007-01-17 21:29       ` Mark Kettenis
2007-01-17 21:38         ` Vladimir Prus
2007-01-17 21:59           ` Frédéric Riss
2007-01-17 22:14             ` Vladimir Prus
2007-01-18  8:00               ` Frederic RISS
2007-01-17 22:17             ` Daniel Jacobowitz
2007-01-18  7:58               ` Frederic RISS
2007-01-18 18:34                 ` Jim Blandy [this message]
2007-01-19 14:28                   ` Denis PILAT
2007-01-20 17:00                     ` Daniel Jacobowitz
2007-01-18 19:59                 ` Daniel Jacobowitz
2007-01-17  6:19     ` Daniel Jacobowitz
2007-01-18 21:13       ` Nick Roberts

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=m33b68b2v4.fsf@codesourcery.com \
    --to=jimb@codesourcery.com \
    --cc=drow@false.org \
    --cc=frederic.riss@gmail.com \
    --cc=frederic.riss@st.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=ghost@cs.msu.su \
    /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