Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: muller@ics.u-strasbg.fr
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] Enhance backtrace for microsoft system DLL calls
Date: Tue, 11 Dec 2007 10:44:00 -0000	[thread overview]
Message-ID: <200712101854.lBAIs91J031646@brahms.sibelius.xs4all.nl> (raw)
In-Reply-To: <000001c83b4a$573b4560$05b1d020$@u-strasbg.fr> 	(muller@ics.u-strasbg.fr)

> From: "Pierre Muller" <muller@ics.u-strasbg.fr>
> Date: Mon, 10 Dec 2007 17:33:05 +0100
> 
>   The main question is whether this patch is acceptable
> for gdb as it is in a i386 common file, while 
> it most probably only applies to MS operating system.

I have no problem with adding this to the generic i386, but I'd prefer
to put this code in a seperate function called
i386_skip_nops(CORE_ADDR pc); And call that function from
i386_analyze_prologue(), instead of adding this code to
i386_analyze_frame_setup().

> Pierre Muller
> 
> ChangeLog entry:
> 
> 2007-12-10  Pierre Muller  <muller@ics.u-strasbg.fr>
> 
> 	* i386-tdep.c (i386_analyze_frame_setup): Ignore `mov %edi,%edi'
> instruction
> 	used at entry of some operating system calls.
> 
> 	
> 
> 
> Index: gdb/i386-tdep.c
> ===================================================================
> RCS file: /cvs/src/src/gdb/i386-tdep.c,v
> retrieving revision 1.246
> diff -u -p -r1.246 i386-tdep.c
> --- gdb/i386-tdep.c     6 Dec 2007 16:32:59 -0000       1.246
> +++ gdb/i386-tdep.c     10 Dec 2007 16:22:21 -0000
> @@ -650,6 +650,17 @@ i386_analyze_frame_setup (CORE_ADDR pc,
> 
>    read_memory_nobpt (pc, &op, 1);
> 
> +  if (op == 0x8b) /* Ignore no-op instruction `mov %edi, %edi' */
> +    {
> +      read_memory_nobpt (pc + 1, &op, 1);
> +      if (op == 0xff)
> +       {
> +         pc += 2;
> +         read_memory_nobpt (pc, &op, 1);
> +       }
> +      else
> +       op = 0x8b;
> +    }
>    if (op == 0x55)              /* pushl %ebp */
>      {
>        /* Take into account that we've executed the `pushl %ebp' that
> 
> 
> 


  parent reply	other threads:[~2007-12-10 18:54 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-10 16:45 Pierre Muller
2007-12-10 17:37 ` Pedro Alves
2007-12-10 18:08   ` Daniel Jacobowitz
2007-12-10 18:41 ` Pedro Alves
2007-12-11 10:44 ` Mark Kettenis [this message]
2007-12-11 17:29   ` Pierre Muller
2008-01-14 10:16     ` [RFC-v2] " Pierre Muller
2008-01-24  0:52       ` Pedro Alves
2008-01-24 17:51       ` Mark Kettenis
2008-01-25 14:16         ` [RFA] i386-tdep.c: Add i386_skip_noop function Pierre Muller
2008-01-25 16:38           ` Joel Brobecker
2008-01-25 16:46             ` [RFA] i386-tdep.c: Add i386_skip_noop function; updated Pierre Muller
2008-01-25 17:05               ` Mark Kettenis
2008-01-25 17:26                 ` Joel Brobecker
2008-01-25 18:50                 ` Pierre Muller

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=200712101854.lBAIs91J031646@brahms.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --cc=gdb-patches@sourceware.org \
    --cc=muller@ics.u-strasbg.fr \
    /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