Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: --pid and --core
Date: Fri, 04 Jan 2008 15:41:00 -0000	[thread overview]
Message-ID: <20080104154110.GC5975@adacore.com> (raw)
In-Reply-To: <477E23F9.7040904@codesourcery.com>

> There's a wrinkle.  The 'int count' variable that was originally
> used in the loop, was also used to do a last resort stack alignment in
> captured_main's entry.
> 
> #if defined (ALIGN_STACK_ON_STARTUP)
>      i = (int) &count & 0x03;
>      if (i != 0)
>        alloca (4 - i);
> #endif
> 
> ALIGN_STACK_ON_STARTUP isn't defined in any target/host
> anymore, and if it was, count is in the middle of the stack frame
> for long and nobody complained.  We can safely
> remove it.

I agree.

> 2008-01-03  Pedro Alves  <pedro@codesourcery.com>
> 
> 	* main.c (captured_main): Remove 'count' varible and the
> 	ALIGN_STACK_ON_ENTRY block that used it.  Error out if --core and
> 	--pid options were issued simultaneously.  If an explicit pid
> 	option was passed, don't fallback to core file.  Detect extra
> 	arguments better in the presence of explicit pid or core
> 	arguments.

This part is OK, please go ahead and commit.

Thanks,
-- 
Joel


  reply	other threads:[~2008-01-04 15:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-03 16:56 Pedro Alves
2008-01-04  5:03 ` Joel Brobecker
2008-01-04 12:20   ` Pedro Alves
2008-01-04 15:41     ` Joel Brobecker [this message]
2008-01-05 12:47     ` Eli Zaretskii
2008-01-05 12:46 ` Eli Zaretskii
2008-01-05 13:09   ` Eli Zaretskii
2008-01-05 17:26     ` Pedro Alves
2008-01-05 17:36       ` Eli Zaretskii
2008-01-05 21:58         ` Pedro Alves

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=20080104154110.GC5975@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@codesourcery.com \
    /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