From: Patrick Palka <patrick@parcs.ath.cx>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Cc: Patrick Palka <patrick@parcs.ath.cx>
Subject: Re: [PATCH] Unset attach_flag when running a new process
Date: Thu, 13 Aug 2015 15:12:00 -0000 [thread overview]
Message-ID: <CA+C-WL8Jzn3GmMQ3+EKDCj9zUWPWCEAXB5PLihvkNhTvGNuGLQ@mail.gmail.com> (raw)
In-Reply-To: <1438270110-23564-1-git-send-email-patrick@parcs.ath.cx>
On Thu, Jul 30, 2015 at 11:28 AM, Patrick Palka <patrick@parcs.ath.cx> wrote:
> We currently set attach_flag when attaching to a process, so we should
> make sure to unset it when forking a new process. Otherwise attach_flag
> would remain set after forking, if the previous process associated with
> the inferior was attached to.
>
> [ I fixed the extended-gdbserver test failure by using
> prepare_for_testing instead of using build_executable + gdb_start. The
> former sets remote exec-file which is what makes the "run" command work as
> expected under extended-gdbserver. ]
>
> gdb/ChangeLog:
>
> * gdb/infcmd.c (run_comand_1): Unset attach_flag.
>
> gdb/testsuite/ChangeLog:
>
> * gdb.base/run-after-attach.exp: New test file.
> * gdb.base/run-after-attach.c: New test file.
Ping.
prev parent reply other threads:[~2015-08-13 15:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-30 1:24 Patrick Palka
2015-07-30 15:28 ` Patrick Palka
2015-07-30 16:24 ` Yao Qi
2015-08-02 20:20 ` Patrick Palka
2015-08-13 16:30 ` Pedro Alves
2015-08-13 17:19 ` Patrick Palka
2015-08-17 13:01 ` Patrick Palka
2015-08-26 16:05 ` Patrick Palka
2015-08-26 17:06 ` Pedro Alves
2015-08-27 0:56 ` Patrick Palka
2015-09-16 16:34 ` Doug Evans
2015-08-13 15:12 ` Patrick Palka [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=CA+C-WL8Jzn3GmMQ3+EKDCj9zUWPWCEAXB5PLihvkNhTvGNuGLQ@mail.gmail.com \
--to=patrick@parcs.ath.cx \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).