Re: NANO core dump on Current
Tim Aslat [EMAIL PROTECTED] wrote: I don't know if I'm the only one with this problem, but here goes. I use Nano (/usr/ports/editors/nano) as my primary text editor, however Iv'e noticed that any time I use -CURRENT (on my notebook) it core dumps when saving a file. This is due to a bug in nano and -CURRENT running by default with malloc option R, which triggers the bug. When I looked, I didn't understand the code well enough to provide a fix, and I have been unable to reach the upstream maintainer by e-mail. -- Christian naddy Weisgerber [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
NANO core dump on Current
Hi All, I don't know if I'm the only one with this problem, but here goes. I use Nano (/usr/ports/editors/nano) as my primary text editor, however Iv'e noticed that any time I use -CURRENT (on my notebook) it core dumps when saving a file. This only happens on -CURRENT of which I have tried several updates (cvsup, make world, make kernel, reboot cycle) without a change in this behaviour. I'm guessing that it's something to do with the C libraries installed under -CURRENT but I'm not sure how to go about finding the error. So far, it's the only thing that doesn't work under -CURRENT on my notebook, so keep up the good work. Regards Tim -- Tim Aslat [EMAIL PROTECTED] Spyderweb Consulting http://www.spyderweb.com.au P: 82243020M: 0401088479 ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NANO core dump on Current
On Mon, Aug 04, 2003 at 08:28:49AM +0930, Tim Aslat wrote: Hi All, I don't know if I'm the only one with this problem, but here goes. I use Nano (/usr/ports/editors/nano) as my primary text editor, however Iv'e noticed that any time I use -CURRENT (on my notebook) it core dumps when saving a file. This only happens on -CURRENT of which I have tried several updates (cvsup, make world, make kernel, reboot cycle) without a change in this behaviour. I'm guessing that it's something to do with the C libraries installed under -CURRENT but I'm not sure how to go about finding the error. Compile the port with CFLAGS=-O -ggdb and obtain a gdb backtrace against the resulting nano binary. Kris pgp0.pgp Description: PGP signature
