From: Daniel Jacobowitz <drow@false.org>
To: Vladimir Prus <ghost@cs.msu.su>
Cc: gdb@sources.redhat.com
Subject: Re: problem debugging assembler functions
Date: Thu, 14 Jul 2005 14:11:00 -0000 [thread overview]
Message-ID: <20050714134548.GB531@nevyn.them.org> (raw)
In-Reply-To: <200507141254.42149.ghost@cs.msu.su>
On Thu, Jul 14, 2005 at 12:54:41PM +0400, Vladimir Prus wrote:
> On Tuesday 14 June 2005 19:27, Daniel Jacobowitz wrote:
>
> > > So, moving 'find_pc_line' above will reasult in extra lookup only if
> > > - the command is stepi/nexti, or
> > > - the first condition evaluates to true (which means we've entered
> > > undebuggable code)
> > >
> > > I have no idea is that's bad or not performance-wise, just clarifying
> > > what's going on.
> >
> > Hmm, that's encouraging! This might be a good improvement, then.
>
> So, is this change going in?
>
> I attach the patch I'm using locally for your reference.
Generally nothing goes in without a patch being submitted (with
changelog, to gdb-patches). It sounds like you're doing a lot of work
on GDB; have you considered getting a copyright assignment on file?
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-07-14 14:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-14 9:23 Vladimir Prus
2005-06-14 14:37 ` Daniel Jacobowitz
2005-06-14 14:54 ` Vladimir Prus
2005-06-14 14:58 ` Daniel Jacobowitz
2005-06-14 15:19 ` Vladimir Prus
2005-06-14 15:27 ` Daniel Jacobowitz
2005-07-14 8:54 ` Vladimir Prus
2005-07-14 14:11 ` Daniel Jacobowitz [this message]
2005-07-14 14:08 ` Vladimir Prus
2005-07-14 14:11 ` Daniel Jacobowitz
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=20050714134548.GB531@nevyn.them.org \
--to=drow@false.org \
--cc=gdb@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