Re: gdb: failed to set signal flags properly for ast()

[phk]

In message <[EMAIL PROTECTED]>, Robe
rt Watson writes:
>
>While debugging the recent pthreads problem, I've started running into
>this:
>
>pid 663 (test), uid 1000: exited on signal 10 (core dumped)
>failed to set signal flags properly for ast()
>failed to set signal flags properly for ast()
>failed to set signal flags properly for ast()
>failed to set signal flags properly for ast()
>failed to set signal flags properly for ast()
>failed to set signal flags properly for ast()

I can't remember how I triggered this, but I have personally
run with this patch for some time:

(NB: Cut&Paste)

Index: kern/subr_trap.c
===================================================================
RCS file: /home/ncvs/src/sys/kern/subr_trap.c,v
retrieving revision 1.239
diff -u -r1.239 subr_trap.c
--- kern/subr_trap.c    28 Dec 2002 01:23:07 -0000      1.239
+++ kern/subr_trap.c    28 Dec 2002 09:05:22 -0000
@@ -74,6 +74,7 @@
 {
        struct proc *p = td->td_proc;
        struct kse *ke = td->td_kse; 
+       static int enough;
 
        CTR3(KTR_SYSC, "userret: thread %p (pid %d, %s)", td, p->p_pid,
             p->p_comm);
@@ -84,7 +85,8 @@
        mtx_lock_spin(&sched_lock);
        if (SIGPENDING(p) && ((p->p_sflag & PS_NEEDSIGCHK) == 0 ||
            (td->td_kse->ke_flags & KEF_ASTPENDING) == 0))
-               printf("failed to set signal flags properly for ast()\n");
+               if (++enough < 10)
+                       printf("failed to set signal flags properly for ast()\n");
        mtx_unlock_spin(&sched_lock);
        PROC_UNLOCK(p);
        mtx_unlock(&Giant);
-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED]         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message