Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Alves <pedro_alves@portugalmail.pt>
Cc: gdb-patches@sourceware.org
Subject: Re: PR/2386 [2/2]: MinGW attach to process without an exec file
Date: Sun, 30 Dec 2007 04:20:00 -0000	[thread overview]
Message-ID: <utzm0x1cb.fsf@gnu.org> (raw)
In-Reply-To: <4776CDA3.90204@portugalmail.pt> (message from Pedro Alves on 	Sat, 29 Dec 2007 22:43:47 +0000)

> Date: Sat, 29 Dec 2007 22:43:47 +0000
> From: Pedro Alves <pedro_alves@portugalmail.pt>
> 
> 2 - PSAPI
>     - Available on NT only, as a seperate dll.

Are you sure it isn't available on 9x?  I have a copy of a disk from
my older 9x machine, and I do see psapi.dll there.

>       I believe that on
>       2000, it comes with one of the service packs.  XP, I believe
>       comes with it.

Yes, on my XP machine I see it as well.

> In any case, we can put a warning in infcmd.c:attach_command,
> when the exec file isn't found, instructing the user to use the
> "file" command.

Yes, if looking up the exec file fails, please issue a clear message.

I also requested for an update of the manual to state the limitations.

> > For the Windows 9x case, I'd prefer if there was just a straightforward
> > error which indicated that what was being attempted is not available on
> > non-NT versions of Windows.
> > 
> 
> But why?  It's not like supporting it in this case is hard.  It can be
> shoved in 30 lines of code, just getting at toolhelp, and iterating over
> all the processes ...  Pretty self contained, doesn't impact anything
> else.

I also think that using ToolHelp32 is an okay solution of this.


  parent reply	other threads:[~2007-12-30  4:18 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
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 [this message]
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=utzm0x1cb.fsf@gnu.org \
    --to=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