Date: Thu, 30 Jul 1998 09:10:01 -0700 (PDT) From: woods@zeus.leitch.com (Greg A. Woods) To: freebsd-bugs@FreeBSD.ORG Subject: Re: bin/7444: login exited on Signal 3, core dumped Message-ID: <199807301610.JAA08051@freefall.freebsd.org>
index | next in thread | raw e-mail
The following reply was made to PR bin/7444; it has been noted by GNATS. From: woods@zeus.leitch.com (Greg A. Woods) To: ru@ucb.crimea.ua Cc: FreeBSD-gnats-submit@FreeBSD.ORG Subject: Re: bin/7444: login exited on Signal 3, core dumped Date: Thu, 30 Jul 1998 12:05:07 -0400 (EDT) [ On Thu, July 30, 1998 at 13:59:31 (+0300), Ruslan Ermilov wrote: ] > Subject: bin/7444: login exited on Signal 3, core dumped > > I have a five dial-in lines. Sometimes login core dumps: > > Jul 29 15:10:15 relay /kernel: pid 12953 (login), uid 0: exited on signal 3 (core dumped) That's trivial to reproduce, and mostly harmless. Just type a bogus user-id at the initial login prompt (i.e. the one given by getty), then a bogus password (eg. <CR>), and at the second login prompt type <CTRL-\> (i.e. the default quit character). You should see the syslog message and a new getty prompt at the same time. SIGQUIT is supposed to cause a core dump -- that's the whole idea behind having it. The fix would be to have login trap and ignore SIGQUIT, but I don't know that it's necessary. Such a fix should be wrapped in #ifndef DEBUG or something similar (IMO). -- Greg A. Woods +1 416 443-1734 VE3TCP <gwoods@acm.org> <robohack!woods> Planix, Inc. <woods@planix.com>; Secrets of the Weird <woods@weird.com> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the messagehome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199807301610.JAA08051>