Date: Wed, 04 Oct 1995 20:33:00 -0700 From: "Justin T. Gibbs" <gibbs@freefall.freebsd.org> To: raoul@cssc-syd.tansu.com.au (Raoul Golan) Cc: gibbs@freefall.freebsd.org (Justin T. Gibbs), freebsd-questions@freebsd.org Subject: Re: gdb problem? libraries, perhaps? (RESOLVED!!!) Message-ID: <199510050333.UAA14791@aslan.cdrom.com> In-Reply-To: Your message of "Thu, 05 Oct 1995 13:15:07 %2B1000." <199510050315.NAA27004@kiwi.cssc-syd.tansu.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
>gdb will fork a shell in order to run its test binary. If that >shell is csh, and .cshrc has an "exec blah" line, then gdb is >in trouble. It will be forking "blah" instead of its test >binary. Is all of this clear? None of this will happen with zsh. > >It looks very much like a generic gdb problem which appears >when combined with csh. I just wish that gdb could be more >"user friendly" in giving proper diagnostics or warnings. >FreeBSD is completely innocent of all this! > >I know I can change my default shell rather than having that >exec in my .cshrc - but I had it that way since I didn't expect >it to cause any problems! Actually, your .csrhc is broken. Anything intended only for interactive shells should be inclosed in: if ($?prompt) then ... ... endif This includes your exec of zsh (which in and of itself is just bad form). -- Justin T. Gibbs =========================================== Software Developer - Walnut Creek CDROM FreeBSD: Turning PCs into workstations ===========================================
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199510050333.UAA14791>