Hello!
Last night, while I was compiling GNU Mach, I got the following assertion
failure:
#v+
ext2fs.static: thread_cancel.c:55: hurd_thread_cancel: Assertion `!
__spin_lock_locked (&ss->critical_section_lock)' failed.
#v-
GNU Mach did not enter the kernel debugger, but was just hanging instead.
I didn't do anything special, so I don't know how I could reproduce it.
Sadly this concides with other reports of the same assertion failing (see
the attached messages,
<URL:http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=46859> and
<URL:http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=195360>).
Regards,
Thomas
--- Begin Message ---
Package: libc0.2
Version: N/A
Severity: critical
Note: I'm sending this report such that this bug will enter the Debian
BTS. The bug has been discussed before on bug-hurd and Roland will
(eventually) look into it. I don't think any immedeate action needs
to be taken by any other party. A summary of the discussion on
bug-hurd follows.
I caught the term server on /dev/console failing the following
assertion in hurd_thread_cancel() (hurd/thread-cancel.c:46):
assert (! __spin_lock_locked (&ss->critical_section_lock));
Since there is no guarantee that the target thread is not in a
critical section, there is obviously something wrong here.
Thomas suggested that there is no need to take the critical section
lock. I believe that taking the critical section lock is necessary to
prevent the target thread from entering a signal handler. Roland will
look into the problem.
Mark
--- End Message ---
--- Begin Message ---
Mark Kettenis:
> I caught the term server on /dev/console failing the following
> assertion in hurd_thread_cancel() (hurd/thread-cancel.c:46):
> assert (! __spin_lock_locked (&ss->critical_section_lock));
Anybody know what became of this bug
<URL:http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=46859&repeatmerged=yes>?
Is it fixed/still reproducible/unknown?
--
Robbe
signature.ng
Description: PGP signature
--- End Message ---
--- Begin Message ---
I got a different Hurd crash than normal. I don't have any more
information than this, sorry. This occured when I was doing an
autobuilder run:
extfs.static: thread-cancel.c:55: hurd_thread_cancel: Assertion `!
__spin_lock_locked (&ss->critical_section_lock)' failed.
The crash is unusual in that the computer didn't reboot like normal,
it was still sitting here when I got up.
Tks,
Jeff Bailey
--- End Message ---
--- Begin Message ---
Mark, (Heya, long time)
I'm just cleaning out the glibc BTS. I pinged Roland about this bug
earlier today, and he indicated that he had no intention of touching
this code until he did a massive overhaul on it.
At a minimum, I'd like to downgrade this bug to 'normal'. Ideally,
I'd like to close it, since it 1) Will never be fixed in a way that's
meaningful to this bug and 2) it's not in a place that Roland ever
looks anyway.
It might be best to submit this in upstreams gnats database to meet
your original need.
Lemme know.
--
learning from failures is nice in theory...
but in practice, it sucks :)
- Wolfgang Jaehrling
--- End Message ---
--- Begin Message ---
Package: hurd
Version: 20020804-1
Tags: unreproducible
After some builds of oskit and gnumach I got the following assertion
failure:
ext2fs.static: thread-cancel.c:55: Assertion `! __spin_lock_locked
(&ss->critical_section_lock)' failed.
libc0.3 is 2.3.1-5.
P.S. The most interesting part is that while compiling oskit, I browsed
a hurd mailing list and the assertion failed just after I hit Enter to
view #116317 ;-)
Regards
--
Ognyan Kulev <[EMAIL PROTECTED]>, "\"Programmer\""
7D9F 66E6 68B7 A62B 0FCF EB04 80BF 3A8C A252 9782
--- End Message ---
_______________________________________________
Bug-hurd mailing list
Bug-hurd@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-hurd
