At 12:05 AM +0100 2/16/03, Friedemann Becker wrote:
http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/47512
this happens only with the above link, i.e. from the pr summary.
searching for the bugid 47512 works (=> not empty)....
someone want to look at this?
The above link worked fine for me. I did not get a blank page.
Also, doing an 'ls' in bash, after starting 'gdb bash', did not
cause any kernel panic. But then it occurred to me that my
login shell was bash (ie, I was already in bash when I typed the
'gdb bash' command).
So, I logged into 'toor', which has /bin/sh as the login shell.
If I logged in at the console, and did a 'gdb bash', then when
I tried to do a 'run' I was told:
Starting program: /usr/local/bin/bash
Cannot exec : No such file or directory
So, then I ssh'ed into 'toor', to make it easier to copy&paste
that error message into this email. Behold, it worked fine.
Well, there was a complaint of:
Starting program: /usr/local/bin/bash
warning: shared library handler failed to enable breakpoint
but other than that warning it worked fine (as did the 'ls').
Sooo, then I checked to see what the difference was between the
two sessions. It turned out that when logging into the console,
the SHELL environment variable was set to the null string. When
I ssh'ed in, it was set to /bin/sh. If I set SHELL on the console
session, then gdb could run bash OK.
I'm not quite sure what all of that means...
All of this was done an a FreeBSD 5.0-CURRENT system, built
on Sat Feb 15 01:34:07 EST 2003
--
Garance Alistair Drosehn = [EMAIL PROTECTED]
Senior Systems Programmer or [EMAIL PROTECTED]
Rensselaer Polytechnic Institute or [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
