From: Stan Shebs <shebs@cygnus.com>
To: gdb-patches@cygnus.com
Cc: gdb-testers@cygnus.com
Subject: No Subject
Date: Mon, 06 Apr 1998 14:16:00 -0000 [thread overview]
Message-ID: <199804062116.OAA19406@andros.cygnus.com> (raw)
In-Reply-To: <199804061141.NAA23820@mail.macqel.be>
Date: Mon, 6 Apr 1998 13:41:37 +0200 (MET DST)
From: "Philippe De Muyter" <phdm@macqel.be>
Am I the only one to have (sometimes) the problem of finding a non-executable
with the same name earlier in my path than the program I want to debug ?
Apparently. :-) But seriously, I don't think this change is a good idea.
While it would work fine for native Unix debugging, it will lose for
just about everything else. For both cross-Unix and embedded debugging
you almost certainly want the programs *not* to be marked as executable,
so that your current host doesn't try to execute them.
However, if you set things up so that this test is only made when
using a Unix child_ops, this would be a useful addition.
Stan
next prev parent reply other threads:[~1998-04-06 14:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-04-06 4:43 Philippe De Muyter
1998-04-06 14:16 ` Stan Shebs [this message]
1998-04-06 14:36 ` Michael Snyder
1998-04-06 15:14 ` Re: Michael Meissner
1999-03-08 7:10 No Subject Andris Pavenis
1999-04-01 0:00 ` Andris Pavenis
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=199804062116.OAA19406@andros.cygnus.com \
--to=shebs@cygnus.com \
--cc=gdb-patches@cygnus.com \
--cc=gdb-testers@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