From: Daniel Jacobowitz <drow@false.org>
To: Fred Fish <fnf@specifix.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Fix problem with scope.exp test, skipping past init0 call
Date: Mon, 13 Feb 2006 15:53:00 -0000 [thread overview]
Message-ID: <20060213155319.GA26917@nevyn.them.org> (raw)
In-Reply-To: <200602131047.30428.fnf@specifix.com>
On Mon, Feb 13, 2006 at 10:47:30AM -0500, Fred Fish wrote:
> > 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.
Hmm, many arches other than i386 are more trusting of line information
than i386 is - but we've historically had some problems with bad
versions of gcc there so it's understandable.
> 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
Ahh - your GCC has unaligned stack support for main. Not surprising
that GDB can't handle this; it's clever, and fresh off the presses.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-02-13 15:53 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 [this message]
2006-02-13 16:05 ` Mark Kettenis
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=20060213155319.GA26917@nevyn.them.org \
--to=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