Bug 91131

Summary: Assertion vgPlain_ksigismember(&uc->uc_sigmask, sigNo) failed
Product: [Developer tools] valgrind Reporter: Clint Olsen <clint>
Component: memcheckAssignee: Julian Seward <jseward>
Status: RESOLVED DUPLICATE    
Severity: normal    
Priority: NOR    
Version: 2.2.0   
Target Milestone: ---   
Platform: Compiled Sources   
OS: Linux   
Latest Commit: Version Fixed In:

Description Clint Olsen 2004-10-11 20:15:18 UTC 
When returning from the debugger, I get this assertion failure.  I have
to kill valgrind with exteme prejudice.

==14590== 
==14590== Debugger has detached.  Valgrind regains control.  We continue.
got signal 17 in LWP 14590 (14590)

valgrind: vg_signals.c:1997 (vg_async_signalhandler): Assertion
`vgPlain_ksigismember(&uc->uc_sigmask, sigNo)' failed.
Comment 1 Tom Hughes 2004-10-12 18:17:04 UTC 
You don't say what kernel and/or distribution you're using, but I suspect you have a kernel without proper gettid support in which case the path on bug 82114 should fix this. Can you try it and confirm whether or not it solves the problem?
Comment 2 Clint Olsen 2004-10-12 18:57:15 UTC 
On Oct 12, Tom Hughes wrote:
> You don't say what kernel and/or distribution you're using, but I suspect
> you have a kernel without proper gettid support in which case the path on
> bug 82114 should fix this. Can you try it and confirm whether or not it
> solves the problem?

Sorry, I got tired of fighting the KDE website after awhile:

Linux plxc2969 2.4.9-45lxset19smp #1 SMP Thu May 6 13:14:38 MST 2004 i686 unknown

It's RedHat something or other.  Our company morphs the heck out of these
things, so it's next to impossible to tell what version.  It's 7.1 or
higher though.

I'll track down this patch and give it a try.

Thanks,

-Clint
Comment 3 Tom Hughes 2004-10-12 18:59:51 UTC 
That kernel looks like it is in the range that has the problem I mentioned. The other bug can be found at:

http://bugs.kde.org/show_bug.cgi?id=82114
Comment 4 Clint Olsen 2004-10-12 19:23:57 UTC 
On Oct 12, Tom Hughes wrote:
> That kernel looks like it is in the range that has the problem I
> mentioned. The other bug can be found at:

That solved it.  Thanks a lot for your help!

-Clint
Comment 5 Tom Hughes 2004-10-12 20:05:49 UTC 
I'll join this to the other bug then.

*** This bug has been marked as a duplicate of 82114 ***

*** This bug has been marked as a duplicate of 82114 ***