From: Lerele <lerele@champenstudios.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Joel Brobecker <brobecker@adacore.com>,
pedro_alves@portugalmail.pt, gdb-patches@sourceware.org
Subject: Re: PR/2386 [2/2]: MinGW attach to process without an exec file
Date: Sat, 29 Dec 2007 14:02:00 -0000 [thread overview]
Message-ID: <47765302.3080305@champenstudios.com> (raw)
In-Reply-To: <ufxxlybhh.fsf@gnu.org>
Eli Zaretskii escribió:
>> Date: Fri, 28 Dec 2007 19:42:28 -0800
>> From: Joel Brobecker <brobecker@adacore.com>
>> Cc: gdb-patches@sourceware.org
>>
>>
>>> Then we should document it somewhere, that we don't support
>>> Windows 9x anymore. Maybe in the NEWS file ?
>>>
>> I personally don't mind declaring the end of support for 9x and NT.
>>
>
> I do. Many 3rd-world countries still have lots of users of older
> systems, and I don't think we should drop their support as yet.
>
> Granted, if Cygwin maintainers don't care about older Windows, then the
> Cygwin port of GDB doesn't have to, either. But the native MinGW port
> does not have to automatically follow that suit, IMO.
>
>
My vote for this one, if it matters. Didn't dare to say it before. Heh.
Plenty of users do still use older Windowses.
If a developer wants to target a Win9x box he/she needs proper debugging
on these, or if a developer is completely hosted on Win9x.
Please do keep in mind these cases, at least for MinGW as Eli says.
> As I wrote elsewhere, the Windows 9x support in the original patch was
> not too hairy, IMO; most of the hair was due to NT support in some
> situations which I don't understand yet (see my questions to Pedro).
> So perhaps even limiting 9x support is not necessary.
>
>
>> But,
>> we don't necessarily have to be that extreme - We could still support
>> Windows 9x but with limitations. Being able to attach the debugger
>> to a PID without specifying the executable is not a critical feature,
>> and if the rest is known to work, it's still a very fine debugger.
>>
>
> I can live with this limitation, provided that:
>
> . We state it in the manual, and
>
> . GDB issues a clear error message when asked to attach to a process
> by PID alone, and is unable to figure out the executable file name.
>
>
>> BTW: Pedro, thanks very much for your work on the Windows port.
>>
>
> Seconded.
>
>
"Thirded".
Quite impressive.
next prev parent reply other threads:[~2007-12-29 14:02 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-28 1:35 Pedro Alves
2007-12-28 4:33 ` Christopher Faylor
2007-12-29 3:37 ` Pedro Alves
2007-12-29 3:50 ` Joel Brobecker
2007-12-29 11:47 ` Eli Zaretskii
2007-12-29 14:02 ` Lerele [this message]
2007-12-29 5:42 ` Joel Brobecker
2007-12-29 12:59 ` Pedro Alves
2007-12-29 14:35 ` Pedro Alves
2007-12-29 18:48 ` Christopher Faylor
2007-12-29 20:15 ` Eli Zaretskii
2007-12-29 22:46 ` Pedro Alves
2007-12-30 3:07 ` Christopher Faylor
2007-12-30 4:32 ` Eli Zaretskii
2007-12-30 20:37 ` Christopher Faylor
2007-12-31 6:35 ` Eli Zaretskii
2007-12-31 8:12 ` Christopher Faylor
2007-12-31 21:38 ` Eli Zaretskii
2007-12-30 20:41 ` Pedro Alves
2007-12-30 4:20 ` Eli Zaretskii
2007-12-31 4:13 ` Pedro Alves
2007-12-29 11:41 ` Eli Zaretskii
2007-12-29 11:33 ` Eli Zaretskii
2007-12-29 14:33 ` Pedro Alves
2007-12-29 16:08 ` Eli Zaretskii
2007-12-30 0:30 ` 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=47765302.3080305@champenstudios.com \
--to=lerele@champenstudios.com \
--cc=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=pedro_alves@portugalmail.pt \
/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