Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sourceware.org
Subject: Re: [rfc] Teach i386 prologue reader about _alloca and __main
Date: Sun, 14 Oct 2007 15:55:00 -0000	[thread overview]
Message-ID: <20071014022434.GA27099@caradoc.them.org> (raw)
In-Reply-To: <471134B9.5060609@portugalmail.pt>

On Sat, Oct 13, 2007 at 10:12:25PM +0100, Pedro Alves wrote:
> The __main call is not i386 specific.  Eg. arm-wince has the same problem.

Yes, but it's only set in i386-specific code and only checked in
i386-specific code; so if it's just a variable in the tdep struct,
then ARM can have a similar one.

If you want to handle it from common code, of course, that's a
different story.

> I'm mostly asking for advice on:
> 
> - Is the gdb-only solution preferable?  That is, the line info
>   currently marks the prologue ending *before* the __main call.
>   Last year's version changed that, this one doesn't.  Does anyone
>   see any problem with that?

I have no strong preference either way.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2007-10-14  2:24 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-13 20:26 Pedro Alves
2007-10-13 21:09 ` Daniel Jacobowitz
2007-10-13 23:20   ` Pedro Alves
2007-10-14 15:55     ` Daniel Jacobowitz [this message]
2007-10-13 21:14 ` Mark Kettenis
2007-10-14  2:24   ` Pedro Alves
2007-12-05 10:11 ` [RFC] testsuite: Skip over function prologue in runto and runto_main Pierre Muller
2007-12-05 22:56   ` Pedro Alves
2007-12-06 16:34     ` Pierre Muller
2007-12-06 17:07       ` 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=20071014022434.GA27099@caradoc.them.org \
    --to=drow@false.org \
    --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