From: cgd@sibyte.com (Chris G. Demetriou)
To: tromey@cygnus.com
Cc: insight@sourceware.cygnus.com
Subject: Re: rename to insight
Date: Wed, 22 Nov 2000 09:42:00 -0000 [thread overview]
Message-ID: <5t7l5vaopo.fsf@highland.sibyte.com> (raw)
In-Reply-To: <mailpost.974851789.4627@postal.sibyte.com>
tromey@cygnus.com (Tom Tromey) writes:
> +exec gdb -w ${1+"$@"}
I believe there's a slight problem with this:
This may get you a different 'gdb' than the one corresponding to the
'insight' being invoked. $PATH is used to find gdb, but not
necessarily to find the 'insight' shell script in this case.
The good news is, i'm pretty sure that pretty much all UNIX-ish
systems invoke shell scripts with a path of the script as $0 (relative
if the script was invoked via a relative path, absolute if via an
absolute path or $PATH) so you could do something like:
gdbpath="`dirname $0`"
exec $gdbpath/gdb ...
(At least, all of the ones i could find right now do, and in general
that's been my experience... and i rely in it in scripts. I dunno
what standards say, if anything.)
of course, 'dirname' isn't as portable as you might like...
chris
next prev parent reply other threads:[~2000-11-22 9:42 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Syd>
[not found] ` <Polk's>
[not found] ` <message>
[not found] ` <of>
[not found] ` <"Tue,>
[not found] ` <"28>
[not found] ` <"Wed,>
[not found] ` <"Mon,>
[not found] ` <01>
[not found] ` <May>
[not found] ` <2000>
[not found] ` <09:07:18>
[not found] ` <-0700>
2000-04-29 7:21 ` make check in itcl Andreas Jaeger
2000-05-01 9:05 ` Syd Polk
2000-05-01 9:27 ` Andreas Jaeger
2000-05-01 10:15 ` Syd Polk
2000-05-01 10:58 ` Andreas Jaeger
2000-05-01 11:21 ` Syd Polk
2000-05-03 10:37 ` Syd Polk
2000-05-03 12:05 ` Andreas Jaeger
2000-05-03 12:37 ` Syd Polk
2000-05-04 2:34 ` Andrew Cagney
[not found] ` <09:17:35>
[not found] ` <-0800>
2000-11-21 16:03 ` rename to insight Tom Tromey
[not found] ` <mailpost.974851789.4627@postal.sibyte.com>
2000-11-22 9:42 ` Chris G. Demetriou [this message]
2000-11-22 10:29 ` Tom Tromey
2000-11-28 9:18 ` Chris G. Demetriou
2000-11-28 9:34 ` Tom Tromey
2000-11-28 12:52 ` Syd Polk
2000-11-28 10:34 Patch: fixlet in gdbtk-cmds.c Tom Tromey
2000-11-28 12:55 ` Syd Polk
2000-11-28 13:46 ` Tom Tromey
2000-11-28 14:47 ` Syd Polk
2000-11-28 17:32 ` Tom Tromey
2000-11-28 23:51 ` Syd Polk
2000-11-29 13:48 ` Tom Tromey
2000-11-29 18:41 ` Syd Polk
2000-11-29 20:07 ` Fernando Nasser
2000-11-30 9:09 ` Tom Tromey
2000-11-30 9:57 ` Fernando Nasser
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=5t7l5vaopo.fsf@highland.sibyte.com \
--to=cgd@sibyte.com \
--cc=insight@sourceware.cygnus.com \
--cc=tromey@cygnus.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).