Re: ast() assert failed ?
On Mon, 15 Jul 2002, Alexander Kabaev wrote: > I am reliably get these messages while using gdb on user processes. This > started long before KSEIII. I haven't managed to duplicate these problems for small user processes and suspect that they have something to do with threaded applications. Can you provide an example with an easy to debug process? Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ast() assert failed ?
On Mon, 15 Jul 2002, Bill Huey wrote: > On Mon, Jul 15, 2002 at 06:00:32PM -0400, Alexander Kabaev wrote: > > Bruce, > > > > I am reliably get these messages while using gdb on user processes. This > > started long before KSEIII. > > Right, I forgot to add that I was also running this program under gdb. > I'm using the most recent -current right now. I have seen these occasionally under a single processor laptop which was not running GDB at the time. Gavin To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ast() assert failed ?
On Mon, Jul 15, 2002 at 06:00:32PM -0400, Alexander Kabaev wrote: > Bruce, > > I am reliably get these messages while using gdb on user processes. This > started long before KSEIII. Right, I forgot to add that I was also running this program under gdb. I'm using the most recent -current right now. bill To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ast() assert failed ?
> Maybe. I got a few of these for my original ast() changes an instant > after I committed them (long before KSEIII), but haven't been able to > duplicate the problem (perhaps because they only occurred for SMP and > I rarely run SMP). I use the following change which prints more info > and fixes a spelling error (*blush*). Bruce, I am reliably get these messages while using gdb on user processes. This started long before KSEIII. -- Alexander Kabaev To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ast() assert failed ?
On Tue, Jul 16, 2002 at 07:04:46AM +1000, Bruce Evans wrote: > Maybe. I got a few of these for my original ast() changes an instant > after I committed them (long before KSEIII), but haven't been able to > duplicate the problem (perhaps because they only occurred for SMP and > I rarely run SMP). I use the following change which prints more info > and fixes a spelling error (*blush*). Hey, Isn't this evil ? Jul 15 14:50:09 finfin kernel: failed to set signal flags properly for ast() Jul 15 14:50:09 finfin kernel: proc java sig 0x400, sigmask 0xfffef007, sigflag 0, astflag 0 Jul 15 14:50:09 finfin kernel: failed to set signal flags properly for ast() Jul 15 14:50:09 finfin kernel: proc java sig 0x400, sigmask 0xfffef007, sigflag 0, astflag 0 It's wierd since all of a sudden this showed up and I think I've been using this kernel for quite a while now (pre-pmap changes). No, wierd pmap problems so far... bill To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ast() assert failed ?
On Mon, 15 Jul 2002, Bill Huey wrote:
> I get a billion of these:
>
> failed to set signal flags proprly for ast()
> failed to set signal flags proprly for ast()
> failed to set signal flags proprly for ast()
> failed to set signal flags proprly for ast()
> failed to set signal flags proprly for ast()
> failed to set signal flags proprly for ast()
>
> Is this KSE related ?
Maybe. I got a few of these for my original ast() changes an instant
after I committed them (long before KSEIII), but haven't been able to
duplicate the problem (perhaps because they only occurred for SMP and
I rarely run SMP). I use the following change which prints more info
and fixes a spelling error (*blush*).
%%%
Index: subr_trap.c
===
RCS file: /home/ncvs/src/sys/kern/subr_trap.c,v
retrieving revision 1.221
diff -u -2 -r1.221 subr_trap.c
--- subr_trap.c 11 Jul 2002 02:18:33 - 1.221
+++ subr_trap.c 12 Jul 2002 22:05:44 -
@@ -82,6 +88,13 @@
mtx_lock_spin(&sched_lock);
if (SIGPENDING(p) && ((p->p_sflag & PS_NEEDSIGCHK) == 0 ||
- (ke->ke_flags & KEF_ASTPENDING) == 0))
- printf("failed to set signal flags proprly for ast()\n");
+ (ke->ke_flags & KEF_ASTPENDING) == 0)) {
+ printf("failed to set signal flags properly for ast()\n");
+ printf(
+ "proc %s sig %#x, sigmask %#x, sigflag %d, astflag %d\n",
+ p->p_comm, ((int *)&p->p_siglist)[0],
+ ((int *)&p->p_sigmask)[0],
+ (p->p_sflag & PS_NEEDSIGCHK) != 0,
+ (ke->ke_flags & KEF_ASTPENDING) != 0);
+ }
mtx_unlock_spin(&sched_lock);
PROC_UNLOCK(p);
%%%
Bruce
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
ast() assert failed ?
Hello, I get a billion of these: failed to set signal flags proprly for ast() failed to set signal flags proprly for ast() failed to set signal flags proprly for ast() failed to set signal flags proprly for ast() failed to set signal flags proprly for ast() failed to set signal flags proprly for ast() Is this KSE related ? bill To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
