Re: (ref5) kdump: Cannout allocate memory
On Mon, 30 Jul 2001, Darren Reed wrote: Using ktrace ref5, I created ~darrenr/ktrace.out with ktrace -i cc ... but trying to print it I get: % kdump -f ~/ktrace.out lout kdump: Cannot allocate memory Is this stack corruption by kdump? ref5:~darrenr/ktrace.out is available for anyone who wants to diagnose this further. This is probably a corrupt ktrace record. Atomic writing of ktrace records seems to have been broken in rev.1.37 of kern_ktrace.c. I've only seen this problem when the output file is written to an nfs filesystem. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
(ref5) kdump: Cannout allocate memory
Using ktrace ref5, I created ~darrenr/ktrace.out with ktrace -i cc ... but trying to print it I get: % kdump -f ~/ktrace.out lout kdump: Cannot allocate memory Is this stack corruption by kdump? ref5:~darrenr/ktrace.out is available for anyone who wants to diagnose this further. FYI: % limit cputime unlimited filesizeunlimited datasize524288 kbytes stacksize 65536 kbytes coredumpsizeunlimited memoryuse unlimited descriptors 2088 memorylockedunlimited maxproc 1043 I can't see that I've got any special malloc debugging things defined either in environment variables or elsewhere. Darren To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
