Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Jason Molenda <jmolenda@apple.com>
Cc: gdb-patches@sources.redhat.com, kettenis@jive.nl
Subject: Re: The gdb x86 function prologue parser
Date: Wed, 08 Jun 2005 14:52:00 -0000	[thread overview]
Message-ID: <u8y1kaoki.fsf@gnu.org> (raw)
In-Reply-To: <85C775AE-3B05-431E-96D2-49EA9D1413E6@apple.com> (message from Jason Molenda on Tue, 7 Jun 2005 22:51:36 -0700)

> Cc: Mark Kettenis <kettenis@jive.nl>
> From: Jason Molenda <jmolenda@apple.com>
> Date: Tue, 7 Jun 2005 22:51:36 -0700
> 
> I can't even begin to imagine how annoyed developers using the FSF
> gdb on x86 must be.

Well, I'm one of the annoyed, although I have no idea whether the
problems that annoyed me would be solved by your patches.  In any
case, thanks.

> --- i386-tdep.c	28 May 2005 16:44:28 -0000	1.213
> +++ i386-tdep.c	8 Jun 2005 05:24:14 -0000
> @@ -21,6 +21,7 @@
>     Foundation, Inc., 59 Temple Place - Suite 330,
>     Boston, MA 02111-1307, USA.  */
>  
> +#include <stdint.h>

I don't think we can use stdint.h freely, as we still don't require a
C9x compiler.  I see you needed it for things like uint8_t and
uint32_t, which should be easily replaceable by suitable standard x86
types.

I also agree with Daniel: it would be nice to find a more graceful way
of storing knowledge about so many instructions.

Last, but not least, I'd surely appreciate some write-up, even in
plain ASCII, about how prologue analyzers in general and the x86 one
in particular work: that stuff is sorely needed in gdbint.texinfo.

TIA


  parent reply	other threads:[~2005-06-08 14:52 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-08  5:51 Jason Molenda
2005-06-08 13:24 ` Daniel Jacobowitz
2005-06-08 16:58   ` Jason Molenda
2005-06-12  7:48     ` Mark Kettenis
2005-06-12  8:44       ` Eli Zaretskii
     [not found]         ` <3364FC4D-63FB-493B-9136-D118F74C13BB@mit.edu>
2005-06-12 13:17           ` Eli Zaretskii
2005-06-12 14:28             ` Daniel Jacobowitz
2005-06-13 18:21             ` Michael Snyder
2005-06-13 19:13               ` Eli Zaretskii
2005-06-08 14:52 ` Eli Zaretskii [this message]
2005-06-08 17:01   ` Jason Molenda
2005-06-08 18:03     ` Eli Zaretskii
2005-06-08 19:58   ` Andreas Schwab
2005-06-09  6:26     ` Jason Molenda
2005-06-09  9:02       ` Andreas Schwab
2005-06-10 20:23         ` Michael Snyder
2005-06-12  7:57       ` Mark Kettenis
2005-06-10 20:29   ` Michael Snyder
2005-06-10 21:18     ` Eli Zaretskii
2005-06-12  7:07 ` Mark Kettenis
2005-06-12  8:50   ` Eli Zaretskii
2005-06-13 22:04   ` Jason Molenda
2005-06-13 22:35     ` Mark Kettenis
2005-06-13 22:51       ` 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=u8y1kaoki.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jmolenda@apple.com \
    --cc=kettenis@jive.nl \
    /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