This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
Re: gdb/247: ../../opcodes/../ltconfig[92]: The fork function failed. There is not enough memory available.
- From: "John David Anglin" <dave at hiauly1 dot hia dot nrc dot ca>
- To: nobody at sources dot redhat dot com
- Cc: gdb-prs at sources dot redhat dot com,
- Date: 26 Nov 2001 19:48:03 -0000
- Subject: Re: gdb/247: ../../opcodes/../ltconfig[92]: The fork function failed. There is not enough memory available.
- Reply-to: "John David Anglin" <dave at hiauly1 dot hia dot nrc dot ca>
The following reply was made to PR gdb/247; it has been noted by GNATS.
From: "John David Anglin" <dave@hiauly1.hia.nrc.ca>
To: dave@hiauly1.hia.nrc.ca (John David Anglin)
Cc: ac131313@cygnus.com, dave.anglin@NRC.CA, gdb-gnats@sources.redhat.com
Subject: Re: gdb/247: ../../opcodes/../ltconfig[92]: The fork function failed. There is not enough memory available.
Date: Mon, 26 Nov 2001 14:44:16 -0500 (EST)
> > As an aside, this is a known problem in GDB 5.1 (see the file gdb/README).
>
> I tried the current cvs last night and the problem is fixed. However, I
> still haven't been able to build a functional gdb for hppa64-hp-hpux11.00 :-(
As a follow up, Jeff Law suggested that defining vfork to fork might
resolve the problem with the child process. That seems to have done
the trick and gdb can now successfully run programs :-)
Dave
--
J. David Anglin dave.anglin@nrc.ca
National Research Council of Canada (613) 990-0752 (FAX: 952-6605)