From: Christopher Faylor <cgf-use-the-mailinglist-please@sourceware.org>
To: gdb-patches@sourceware.org
Subject: Re: PR/2386 [2/2]: MinGW attach to process without an exec file
Date: Mon, 31 Dec 2007 08:12:00 -0000 [thread overview]
Message-ID: <20071231063534.GA7572@ednor.casa.cgf.cx> (raw)
In-Reply-To: <ur6h3wlgy.fsf@gnu.org>
On Mon, Dec 31, 2007 at 06:13:01AM +0200, Eli Zaretskii wrote:
>> Date: Sun, 30 Dec 2007 12:08:28 -0500
>> From: Christopher Faylor <cgf-use-the-mailinglist-please@sourceware.org>
>>
>> >> + warning(_("working version of psapi.dll not found. DLL and executable filenames may not be available."));
>> >
>> >This is not a useful message, IMHO. I, as a user, would not know what
>> >to do with it. We need to says specifically that attach without an
>> >exec file name will not work, and that users should use `file'
>> >etc. commands to work around.
>>
>> Could you give me some exact wording, please? Is this adequate?
>>
>> "working version of psapi.dll not found. Use `file' and `dll' commands to specifically load symbols."
>>
>> ?
>
>IMO, the first sentence is a technicality that doesn't help. How
>about the following instead?
>
> Cannot find executable file by PID. Use "file" and "dll" commands
> to load symbols.
That's not entirely accurate either since it's not just the ability to
load executable files by pid that is affected, it's also the ability to
figure out any dll names loaded in the executable.
Cannot determine correspondence between load addresses and dll/executable filenames. Use "file" and "dll" commands to load symbols.
?
>> Note, that this is actually an enhancement for what has existed in gdb
>> for years.
>
>Sure, but we want to improve things, right?
Uh, yeah. That's why I added the message. I wasn't sure you quite
understood that, for the most part, this wasn't new functionality.
cgf
next prev parent reply other threads:[~2007-12-31 6:35 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 [this message]
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=20071231063534.GA7572@ednor.casa.cgf.cx \
--to=cgf-use-the-mailinglist-please@sourceware.org \
--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