From: Elena Zannoni <ezannoni@cygnus.com>
To: Fernando Nasser <fnasser@cygnus.com>
Cc: david@llamedos.org, gdb-patches@sources.redhat.com,
Elena Zannoni <ezannoni@cygnus.com>
Subject: Re: [PATCH] Stale FIXME
Date: Wed, 06 Jun 2001 14:46:00 -0000 [thread overview]
Message-ID: <15134.42137.106652.218525@kwikemart.cygnus.com> (raw)
In-Reply-To: <3B0C4192.1C68898C@cygnus.com>
Fernando Nasser writes:
> David Deephanphongs wrote:
> >
> > There appears to be a stale FIXME in main.c - it warns about the
> > argument after the program-name (corearg):
> > /* FIXME: The documentation says this can be a "ProcID". as well. */
> >
> > GDB /does/ treat the corearg as a PID, though.
> > First it tries to open corearg as a core-file. If that fails, it attempts
> > to use it as a PID (main.c:615-623).
>
> Yes, and I use it all the time to debug gdb with gdb. That was a badly worded FIXME text. It was supposed to say that we should not be overloading variables and filling them with something that is not related to its name -- 4 bytes is a small price to pay for clarity IMO.
>
> I still would like to keep a note there that saying that corearg may be a PID and not a core file name. Something like:
>
> /* COREARG can be the name of a core file or
> the "ProcID" of a process we should attach to. */
>
> Can you submit your patch with the replacement text? I will ask permission to Elena and check it in.
>
I see, you added the comment... :-) So I trust you know what you meant
to say. Please, modify the comment as you indicated above.
Thanks
Elena
> Thanks for the catch.
>
> --
> Fernando Nasser
> Red Hat - Toronto E-Mail: fnasser@redhat.com
> 2323 Yonge Street, Suite #300
> Toronto, Ontario M4P 2C9
>
next prev parent reply other threads:[~2001-06-06 14:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-22 0:24 David Deephanphongs
2001-05-23 16:03 ` Fernando Nasser
2001-06-06 14:46 ` Elena Zannoni [this message]
2001-06-06 15:02 ` Fernando Nasser
2001-06-06 18:42 ` David Deephanphongs
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=15134.42137.106652.218525@kwikemart.cygnus.com \
--to=ezannoni@cygnus.com \
--cc=david@llamedos.org \
--cc=fnasser@cygnus.com \
--cc=gdb-patches@sources.redhat.com \
/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