Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Frederic RISS <frederic.riss@st.com>,
		Jim Blandy <jimb@codesourcery.com>
Cc: "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 19:59:00 -0000	[thread overview]
Message-ID: <20070118195916.GA21617@nevyn.them.org> (raw)
In-Reply-To: <m33b68b2v4.fsf@codesourcery.com> <1169107060.3288.126.camel@localhost.localdomain>

On Thu, Jan 18, 2007 at 08:57:40AM +0100, Frederic RISS wrote:
> > For instance:
> >   - We can speed up the psymtab lookup which currently shows up in
> >     profiles.  A coworker of mine gave me some clever ideas on how
> >     to do this if anyone wants to try it :-)
> 
> Hehe. What's the idea? maybe someone will pick it up.

Rouhly speaking, recording all of the intervals covered by psymbols
on a per objfile basis.  If you avoid using the faster lookup mechanism
in the presence of overlays, you can assume a single best symbol
covering each address and roughly non-overlapping (but not quite).

It's just going to be a matter of slogging through it.  I expect we'd
get a bunch of splay trees.

On Thu, Jan 18, 2007 at 10:34:39AM -0800, Jim Blandy wrote:
> 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.

Absolutely.  As fast as possible, but no faster :-)

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

Yes please.

-- 
Daniel Jacobowitz
CodeSourcery


  parent reply	other threads:[~2007-01-18 19:59 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
2007-01-19 14:28                   ` Denis PILAT
2007-01-20 17:00                     ` Daniel Jacobowitz
2007-01-18 19:59                 ` Daniel Jacobowitz [this message]
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=20070118195916.GA21617@nevyn.them.org \
    --to=drow@false.org \
    --cc=frederic.riss@gmail.com \
    --cc=frederic.riss@st.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=ghost@cs.msu.su \
    --cc=jimb@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