Date: Wed, 31 Oct 2001 17:10:01 -0800 (PST) From: "Andrew R. Reiter" <arr@watson.org> To: freebsd-bugs@FreeBSD.org Subject: Re: bin/31678: A bug in handling an error reading a CD-ROM results in core. Message-ID: <200111010110.fA11A1s17562@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR bin/31678; it has been noted by GNATS. From: "Andrew R. Reiter" <arr@watson.org> To: FreeBSD-gnats-submit@FreeBSD.ORG Cc: Subject: Re: bin/31678: A bug in handling an error reading a CD-ROM results in core. Date: Wed, 31 Oct 2001 20:03:47 -0500 (EST) I should have added: Oct 31 16:53:57 rakahanga /boot/kernel/kernel: acd0: READ_BIG - MEDIUM ERROR asc =0x02 ascq=0x00 error=0x00 Oct 31 16:53:57 rakahanga /boot/kernel/kernel: pid 7843 (sysinstall), uid 0: exi ted on signal 11 (core dumped) that error from /var/log/messages at the time of the core. On Wed, 31 Oct 2001, Andrew R. Reiter wrote: : :>Number: 31678 :>Category: bin :>Synopsis: A bug in handling an error reading a CD-ROM results in core. :>Confidential: no :>Severity: serious :>Priority: medium :>Responsible: freebsd-bugs :>State: open :>Quarter: :>Keywords: :>Date-Required: :>Class: sw-bug :>Submitter-Id: current-users :>Arrival-Date: Wed Oct 31 17:00:01 PST 2001 :>Closed-Date: :>Last-Modified: :>Originator: Andrew R. Reiter :>Release: FreeBSD 5.0-CURRENT i386 :>Organization: :>Environment: :System: FreeBSD rakahanga 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Mon Oct 29 06:39:1 :1 GMT 2001 root@:/usr/obj/usr/src/sys/GENERIC i386 : : :>Description: :When trying to use an unmounted CD-ROM in sysinstall for post-install configure :in order to install packages, it can cause a core if : : :>How-To-Repeat: :Insert a 4.4 release CD on a -current box, run sysinstall. Go to the configure :menu, and then to the packages installation menu and choose CD-ROM/DVD. :It will let you know that the CD-ROM in the drive is a 4.4-RELEASE disk and :you must hit OK, then it will ask if you wish to continue despite this, and :you hit YES. It will then attempt to read thte INDEX file and then core. :The GDB bt i got was: :(gdb) bt :#0 0x8054b3f in sigprocmask () :#1 0x281c5400 in .curbrk () from /usr/lib/libc.so.5 :#2 0x8055841 in sigprocmask () :#3 0x804db60 in sigprocmask () :#4 0x280b6025 in dialog_menu () from /usr/lib/libdialog.so.4 :#5 0x8052eb8 in sigprocmask () :#6 0x8052cae in sigprocmask () :#7 0x805294a in sigprocmask () :#8 0x280b6025 in dialog_menu () from /usr/lib/libdialog.so.4 :#9 0x8052eb8 in sigprocmask () :#10 0x805adb7 in sigprocmask () :#11 0x804b2c5 in sigprocmask () :(gdb) info all-register :eax 0x80aa290 134914704 :ecx 0x5 5 :edx 0x0 0 :ebx 0x0 0 :esp 0xbfbfdd08 0xbfbfdd08 :ebp 0xbfbfefa0 0xbfbfefa0 :esi 0x80c0b00 135006976 :edi 0x0 0 :eip 0x8054b3f 0x8054b3f :eflags 0x10246 66118 :cs 0x1f 31 :ss 0x2f 47 :ds 0x2f 47 :es 0x2f 47 :fs 0x2f 47 :gs 0x2f 47 : :>Fix: :Since the GDB stack trace said sigprocmask, I started hunting around for :signal problems.. I did find a poorly design signal handler (contained :non-signal safe functions) but I am kinda doubting that it is the real :source of the problem. : : :>Release-Note: :>Audit-Trail: :>Unformatted: : :To Unsubscribe: send mail to majordomo@FreeBSD.org :with "unsubscribe freebsd-bugs" in the body of the message : *-------------................................................. | Andrew R. Reiter | arr@fledge.watson.org | "It requires a very unusual mind | to undertake the analysis of the obvious" -- A.N. Whitehead To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200111010110.fA11A1s17562>