This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: gcc 3.1 and gdb 5.2?
- From: Joe Buck <Joe dot Buck at synopsys dot com>
- To: schwab at suse dot de (Andreas Schwab)
- Cc: doug at ikos dot com, gcc at gcc dot gnu dot org
- Date: Fri, 14 Jun 2002 08:22:25 -0700 (PDT)
- Subject: Re: gcc 3.1 and gdb 5.2?
> |> Is there any way to configure gdb *not* to load your
> |> .cshrc upon invocation? That is nasty behavior.
>
> It's not gdb that loads .cshrc, but csh does it.
The user does not expect gdb to invoke a shell. The user is in csh
and has already changed environment variables and is not expecting
gdb to start up a new shell and wipe out the changes.
One possible fix is this: gdb could know about csh and tcsh's special
behavior, and invoke it with the -f flag.
> |> Moreover, if you get into gdb and LD_LIBRARY_PATH
> |> (or any other env variable) is obviously set wrong,
> |> and you do "show env LD_LIBRARY_PATH" inside gdb,
> |> it will show you the environment of your original shell,
> |> *not* gdb's actual environment. Even nastier.
>
> This *is* gdb's actual enviroment, it's the shell that mangles it.
No, it's not. When the user types the command "gdb", the environment
is one way; within gdb it is another way. No user would expect such
a thing.