Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: fnf@specifix.com
Cc: drow@false.org, gdb-patches@sourceware.org
Subject: Re: [PATCH] Fix problem with scope.exp test, skipping past init0 call
Date: Mon, 13 Feb 2006 16:05:00 -0000	[thread overview]
Message-ID: <200602131604.k1DG4n9Y025733@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <200602131047.30428.fnf@specifix.com> (message from Fred Fish on 	Mon, 13 Feb 2006 10:47:30 -0500)

> From: Fred Fish <fnf@specifix.com>
> Date: Mon, 13 Feb 2006 10:47:30 -0500
> 
> On Monday 13 February 2006 10:39, Daniel Jacobowitz wrote:
> > What platform and compiler version is this?  It doesn't fail for me.
> 
> Fedora Core 4, using the latest development gcc while running the]
> gdb testsuite.

Hmm, if you didn't commit the fix yet, can you please hold off doing
that for a bit?  From your explanation below, it turns out that this
might have caught a genuine genuine GDB bug.  By "fixing" this we're
likely not to notice that.  And if this would have been a GCC bug that
would have been fixed in the official release, there would have been
no reason to have added a workaround either.

> > Well, that's supposed to skip a call to __main(), which GCC generates
> > on very few platforms... stopping at the opening brace is definitely
> > a bug in its own right, in the debug info or in the prologue skipper.
> 
> The problem is that gcc now generates prologues that the prologue skipper
> isn't prepared to handle.
> 
> The latest gcc generates prologues like:
> 
> main:
>         leal    4(%esp), %ecx
>         andl    $-16, %esp
>         pushl   -4(%ecx)
>         pushl   %ebp
>         movl    %esp, %ebp
>         pushl   %ecx
>         call    foo

Hmm, what's happening here?  Looks like the first three instructions
are aligning the stack on a 16-byte boundary.  Why is GCC doing that?

Mark


  parent reply	other threads:[~2006-02-13 16:05 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-12 20:10 Fred Fish
2006-02-13  6:16 ` Jim Blandy
2006-02-13 15:39 ` Daniel Jacobowitz
2006-02-13 15:47   ` Fred Fish
2006-02-13 15:53     ` Daniel Jacobowitz
2006-02-13 16:05     ` Mark Kettenis [this message]
2006-02-13 16:08       ` Daniel Jacobowitz
2006-02-13 16:19       ` Fred Fish
2006-02-13 16:49         ` Mark Kettenis
2006-02-13 17:47           ` Jim Blandy
2006-02-13 17:54             ` Jim Blandy
2006-02-13 17:57               ` Jim Blandy
2006-02-13 18:08                 ` Mark Kettenis
2006-03-02  0:01             ` Michael Snyder
2006-03-02  6:09               ` Jim Blandy
2006-02-13 18:39           ` Fred Fish

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=200602131604.k1DG4n9Y025733@elgar.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --cc=drow@false.org \
    --cc=fnf@specifix.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