Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@cygnus.com>
To: Michal Ludvig <mludvig@suse.cz>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] x86_64_skip_prologue
Date: Sat, 23 Mar 2002 11:01:00 -0000	[thread overview]
Message-ID: <3C9CD0EA.50809@cygnus.com> (raw)
In-Reply-To: <3C9760B6.7040900@suse.cz>

> Kevin Buettner wrote:
> 3) Now pc points to the first line of the sourcecode of the function (usually opening '{'). If the next line with debuginfo has pc within bounds of this function, we will return this pc instead.
> 
> You might want to take a look at some of the other prologue analyzers.
> In particular, you might want to consider calling find_pc_line() instead
> of accessing the data structures directly.
> 
> Most of other *_skip_prologue functions pretend, that prolog is an always-the-same sequence of instructions, what is not the case on x86-64. I can't see an approach other than the one I have chosen.
> Of course I can use other structures and maybe some macros, but the concept will remain. Or is there another way?
> 
> Why should I preferably use find_pc_line()? It gives me the same symtab as find_pc_symtab() does... Anyway I have rewritten the code to use it.
> 
> BTW, you might want to run your code through indent.
> 
> Sorry, I'm not yet used to follow GNU coding style. Hopefully now it is better ;-)
> Michal Ludvig

The script gdb_indent.sh will always fix any problems :-)

Yes, ok.  (Don't forget the changelog when posting patches).

Andrew



      parent reply	other threads:[~2002-03-23 19:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-15 10:22 Michal Ludvig
2002-03-15 10:41 ` Kevin Buettner
2002-03-19  8:01   ` Michal Ludvig
2002-03-22  2:57     ` Michal Ludvig
2002-03-23 11:01     ` 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=3C9CD0EA.50809@cygnus.com \
    --to=ac131313@cygnus.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=mludvig@suse.cz \
    /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