From: Pedro Alves <pedro@codesourcery.com>
To: Doug Evans <dje@google.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] Fix build failure [was Re: [RFC] fork in multi-threaded apps, per-thread pending_fork, other follow-fork cleanups.]
Date: Sun, 24 May 2009 20:50:00 -0000 [thread overview]
Message-ID: <200905242150.12317.pedro@codesourcery.com> (raw)
In-Reply-To: <e394668d0905241327l7790a531l9cd003fcae1ee809@mail.gmail.com>
On Sunday 24 May 2009 21:27:30, Doug Evans wrote:
> gcc's not smart enough to detect it's actually ok.
Sigh...
> 2009-05-24 Doug Evans <dje@google.com>
>
> * infrun.c (follow_fork): Initialize new step_* locals
> to avoid "may be used uninitialized" warnings.
Ok, thanks.
--
Pedro Alves
prev parent reply other threads:[~2009-05-24 20:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-24 20:27 Doug Evans
2009-05-24 20:50 ` Pedro Alves [this message]
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=200905242150.12317.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=dje@google.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