Re: csh on arm failure?
- From: Mark Peek <mp@xxxxxxxxxxx>
- Date: Tue, 15 May 2007 11:48:46 -0700
On 5/15/07 6:56 AM, Ricardo Nabinger Sanchez wrote:
On Tue, 15 May 2007 16:30:35 +0300
Krassimir Slavchev <krassi@xxxxxxxxxxx> wrote:
#0 0x20204bb0 in kill () from /lib/libc.so.7
#1 0x20200370 in abort () from /lib/libc.so.7
#2 0x00045fe4 in malloc (nbytes=16)
#3 0x00045fe4 in malloc (nbytes=16)
Any chances that this relates to Steven's PR 112408? (Not the gdb part, just
the tcsh regression.)
No, this is different. The tcsh malloc is showing it is out of memory and aborting. The thing I don't understand is the malloc is coming from tcsh instead of using the system malloc. Looking at this file:
/* we want to use the system malloc when we install as /bin/csh */
/* Use LC_MESSAGES locale category to open the message catalog */
#define MCLoadBySet NL_CAT_LOCALE
#define BUFSIZE 8192
The SYSMALLOC define should cause it to use the system malloc and not the tcsh malloc. Could __FreeBSD__ not be defined?
Also, it is odd that it is out of memory in the first place. Has it worked before? Is there something that changed in the arm memory allocation schemes?
freebsd-current@xxxxxxxxxxx mailing list
To unsubscribe, send any mail to "freebsd-current-unsubscribe@xxxxxxxxxxx"
- Prev by Date: RE: Releasing MSI Resources in a Module Causes Kernel Panic on -CURRENT
- Next by Date: Re: HEDSUP: man -k cleanup (man -k RAID, some bits are missing)
- Previous by thread: Re: csh on arm failure?
- Next by thread: Re: csh on arm failure?