Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
To: "'Joel Brobecker'" <brobecker@adacore.com>
Cc: <gdb-patches@sourceware.org>
Subject: RE: [RFC] Improve amd64 prologue analysis
Date: Fri, 19 Nov 2010 08:15:00 -0000	[thread overview]
Message-ID: <004201cb87c1$dab95cd0$902c1670$@muller@ics-cnrs.unistra.fr> (raw)
In-Reply-To: <20101118172209.GE2634@adacore.com>



> -----Message d'origine-----
> De : gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] De la part de Joel Brobecker
> Envoyé : jeudi 18 novembre 2010 18:22
> À : Pierre Muller
> Cc : gdb-patches@sourceware.org
> Objet : Re: [RFC] Improve amd64 prologue analysis
> 
> > Free Pascal for x86_64 (amd64) CPU generates losts of functions
> > that do not use RBP as a frame pointer.
> > I tried to improve amd64-tdep.c to better cope
> > with this case.
> 
> I thought that on amd64, we weren't going to have prologue parsers
> and rely on frame unwinding info instead?   At AdaCore, we have the
> same sort of things because of Windows where the system code (mostly
> system DLLs) does not have the unwinding info in DWARF format. But
> for code generated by us, we have all the debugging information needed
> to unwind without parsing the prologue, even on Windows64.

  Does this means that we should only use that code
if no dwarf debug info is available?
  The problem currently on Windows-64bit generated code
is that dwarf debug information is more 
deeply broken than stabs, so that I am still mainly using stabs
(especially to debug dwarf problems...).

  In any case it, this code would still be useful for 
frames that have no debug information at all, as it allows 
for frame that do not uses RBP to figure out the correct offset for
RSP, and thus the correct caller frame position.

Pierre


  reply	other threads:[~2010-11-19  8:15 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-15 17:28 Pierre Muller
2010-11-18 17:22 ` Joel Brobecker
2010-11-19  8:15   ` Pierre Muller [this message]
2010-11-19 17:20     ` Joel Brobecker
2010-11-19 22:50       ` Pierre Muller
2010-12-14  7:05         ` Joel Brobecker
2010-12-14  9:58           ` Pedro Alves
2010-12-15 23:07           ` Mark Kettenis
2010-12-16  4:15             ` Joel Brobecker
2010-11-24 21:19     ` Mark Kettenis
2010-11-24 22:15       ` Joel Brobecker
2010-11-24 22:26         ` Joel Brobecker
2010-11-25 13:39           ` Mark Kettenis
2010-11-25 16:30             ` Joel Brobecker
2010-11-25 19:19               ` Kai Tietz
2010-11-24 22:17       ` Joel Brobecker

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='004201cb87c1$dab95cd0$902c1670$@muller@ics-cnrs.unistra.fr' \
    --to=pierre.muller@ics-cnrs.unistra.fr \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    /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