This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Weird x86 Linux/GNU crashes
- From: Daniel Jacobowitz <drow at mvista dot com>
- To: Stan Shebs <shebs at apple dot com>
- Cc: Joe Buck <Joe dot Buck at synopsys dot com>, "David S. Miller" <davem at redhat dot com>,mark at codesourcery dot com, hjl at lucon dot org, gcc at gcc dot gnu dot org
- Date: Wed, 31 Jul 2002 13:33:41 -0400
- Subject: Re: Weird x86 Linux/GNU crashes
- References: <200207311633.JAA24705@atrus.synopsys.com> <3D48162D.9060000@apple.com>
On Wed, Jul 31, 2002 at 09:54:05AM -0700, Stan Shebs wrote:
> Joe Buck wrote:
>
> >David Miller writes:
> >
> >>GDB exec's a shell to setup your environment properly then execute the
> >>program to be debugged. In this way GDB's environemnt doesn't need
> >>to be altered among other things.
> >>
> >
> >This "feature" of gdb has caused me nothing but pain over the years; no
> >other program thinks it needs to "setup your environment properly" rather
> >than just use the environment as is. In almost every case where I have
> >trouble, the environment *was* set up properly before GDB destroyed it by
> >exec-ing a shell. Life tends to be worse for csh/tcsh users, but bash
> >users can also be messed up.
> >
> >Unfortunately, gdb's developers like it this way, so the rest of us just
> >have to work around the damage.
> >
> Drifting OT I suppose, but I vaguely remember a discussion about adding
> an option to choose not to run a subshell at all. Cygwin has that option
> for instance, and I can't imagine it would be that hard to add for Unix
> too. Is there a PR on this?
I don't think so. Please file one and I'll look into it in a couple of
weeks.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer