From: Michael Snyder <msnyder@specifix.com>
To: gdb@sourceware.org
Cc: Nicolas Bonifas <nicolas.bonifas@free.fr>
Subject: Should we install gcore.sh (and a gcore.1 man page)?
Date: Wed, 24 Oct 2007 22:01:00 -0000 [thread overview]
Message-ID: <1193262980.16917.16.camel@localhost.localdomain> (raw)
The offered contribution, by Nicolas Bonifas, of a man page
for the gcore shell script has raised a question vis a vis
gdb's install script.
We have this shell script in our source tree, which invokes
gdb and makes it run the "gcore" command on a specified process.
This was, I believe, to mimic a 'gcore' command utility from
Sun (or some such).
But we've never installed the gcore shell script.
Should we? Should we go ahead and put it into $<install>/bin?
In which case we might want to accept the contributed man page
and install that as well?
Apparently Debian's package installer does this, renaming the
script to just "gcore" in the process.
Michael
next reply other threads:[~2007-10-24 22:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-24 22:01 Michael Snyder [this message]
2007-10-24 22:10 ` Joel Brobecker
2007-10-24 22:14 ` Michael Snyder
2007-10-24 22:24 ` Joel Brobecker
2007-10-25 0:21 ` Michael Snyder
2007-10-25 0:41 ` Joel Brobecker
2007-11-05 9:30 ` Nicolas Bonifas
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=1193262980.16917.16.camel@localhost.localdomain \
--to=msnyder@specifix.com \
--cc=gdb@sourceware.org \
--cc=nicolas.bonifas@free.fr \
/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).