Re: Proc failure with gcc-2.95.2

2000-02-28 Thread Marcus Brinkmann
Hi, On Mon, Feb 28, 2000 at 07:15:08PM +, Chris Lingard wrote: > Breakpoint 1, main (argc=134529024, argv=0x1, envp=0x11affa8) > at ../../proc/main.c:64 > 64struct argp argp = { 0, 0, 0, "Hurd process server" }; > (gdb) info threads > * 1 thread 125.1 main (argc=134529024, argv=0

Re: Proc failure with gcc-2.95.2

2000-02-28 Thread Chris Lingard
> > > > > fetch inferior registers: 1: Invalid thread > > This is never that useful a command. Do `info threads' here. > gdb does Attaching to program `/hurd/proc', pid 99 warning: Can't modify tracing state for pid 99: No signal thread fetch inferior registers: 1: Invalid thread (gdb) info

Re: fixed #! exec bug aka "/dev/fd/3: Bad file descriptor"

2000-02-28 Thread Jeff Bailey
On Mon, Feb 28, 2000 at 03:26:59AM -0500, Roland McGrath wrote: > > Are you beginning to suggest doing partial updates in general to the system? > > I suggest nothing, I just try to provide full information to enable > whatever choices people might want to make. If you are not already > interest

Re: fixed #! exec bug aka "/dev/fd/3: Bad file descriptor"

2000-02-28 Thread Roland McGrath
> Are you beginning to suggest doing partial updates in general to the system? I suggest nothing, I just try to provide full information to enable whatever choices people might want to make. If you are not already interested in building the hurd yourself and doing delicate updates by hand, then