This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
Re: gdb/1622: vfork; no such file; root; access rights??
- From: Daniel Jacobowitz <drow at false dot org>
- To: nobody at sources dot redhat dot com
- Cc: gdb-prs at sources dot redhat dot com,
- Date: 25 Apr 2004 15:18:01 -0000
- Subject: Re: gdb/1622: vfork; no such file; root; access rights??
- Reply-to: Daniel Jacobowitz <drow at false dot org>
The following reply was made to PR gdb/1622; it has been noted by GNATS.
From: Daniel Jacobowitz <drow@false.org>
To: Andreas <zickzack@w84u.org>
Cc: gdb-gnats@sources.redhat.com
Subject: Re: gdb/1622: vfork; no such file; root; access rights??
Date: Sun, 25 Apr 2004 11:14:40 -0400
On Sun, Apr 25, 2004 at 09:06:43AM -0600, Andreas wrote:
> Thanks you very much for your answer. You were right; $SHELL was not
> set. I found out, that for some reason "/bin/bash" was missing in
> the user line within /etc/passwd.
>
> After adding it gdb works fine also under user. I have no clue
> why/when the /etc/passwd file changed (probably during an automated
> update...?)
>
> To improve the debugging in such a case for a not so experienced
> programmer, a better error message like "$SHELL not set" would be much
> more helpful. So I suggest to add this check into gdb since gdb seems
> to rely on it.
I need to fix the use of $SHELL entirely. Haven't had time.
> Another questing: Is there a way to make strace follow the child, who
> fails in this case?
strace -fF
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer