From: Jon Turney <jon.turney@dronecode.org.uk>
To: Takashi Yano <takashi.yano@nifty.ne.jp>,
The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: GDB looses pgrp setting in the terminal for debugged process after break.
Date: Mon, 17 Jan 2022 18:57:05 +0000 [thread overview]
Message-ID: <abd04421-8a46-3437-f86e-3fd1c1754a58@dronecode.org.uk> (raw)
In-Reply-To: <20210507173340.9741cec791c2bfbb9edee4f2@nifty.ne.jp>
On 07/05/2021 09:33, Takashi Yano via Cygwin wrote:
> On Thu, 6 May 2021 21:31:27 +0100
> Jon Turney wrote:
>> On 02/05/2021 17:16, Takashi Yano via Cygwin wrote:
>>> On Sat, 6 Feb 2021 00:26:54 +0900
>>> Takashi Yano wrote:
>>>> On Fri, 5 Feb 2021 19:34:57 +0900
>>>> Takashi Yano wrote:
>>>>> On Tue, 26 Jan 2021 12:14:02 +0900
>>>>> Takashi Yano wrote:
>>>>>> Hi GDB maintainer,
>>
>> Sorry! I meant to go back and look at this, but I forgot.
>>
>> Thanks for reminding me!
>
> Thanks for replying.
I've included this patch in the gdb-11.22-1 test package.
I don't think this patch is upstreamable as is.
I guess I'd like something which stores both winpid and cygwin pid,
where the winpid is only used inside windows-nat with Win32 API calls,
and the cygwin pid is the pid used by core code in POSIX API calls.
Unfortunately, writing that seems complex, as the
CW_WINPID_TO_CYGWIN_PID mapping can't be done immediately after
CreateProcess(), as some code in the inferior needs to run first (since
to perform the mapping, it uses links created by
pinfo::create_winpid_symlink(), called in crt0)
prev parent reply other threads:[~2022-01-17 18:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-26 3:14 Takashi Yano
2021-02-05 10:34 ` Takashi Yano
2021-02-05 15:26 ` Takashi Yano
2021-05-02 16:16 ` Takashi Yano
2021-05-06 20:31 ` Jon Turney
2021-05-07 8:33 ` Takashi Yano
2022-01-17 18:57 ` Jon Turney [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=abd04421-8a46-3437-f86e-3fd1c1754a58@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=cygwin@cygwin.com \
--cc=takashi.yano@nifty.ne.jp \
/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).