https://bugs.kde.org/show_bug.cgi?id=372504
Philippe Waroquiers changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=372504
--- Comment #25 from Philippe Waroquiers ---
Looking in m_signals.c : it looks like some special support
for sigsuspend/rt_sigsuspend is supported to be done, e.g. using
tmp_sig_mast. See a.o. the following comments in m_signals.c:2012
/* At this
https://bugs.kde.org/show_bug.cgi?id=372504
--- Comment #24 from Philippe Waroquiers ---
The attached file maskvgkill.c reproduces the problem.
It terminates when run natively, under V, it loops.
It seems that effectively, it is enough to mask sigvgkill
to have exit causing an infinite loop.
--
https://bugs.kde.org/show_bug.cgi?id=372504
--- Comment #23 from Philippe Waroquiers ---
Created attachment 102315
--> https://bugs.kde.org/attachment.cgi?id=102315&action=edit
program not dying because it masks sigvgkill
--
You are receiving this mail because:
You are watching all bug change
https://bugs.kde.org/show_bug.cgi?id=372504
--- Comment #22 from Philippe Waroquiers ---
(In reply to Tom Hughes from comment #21)
> Presumably valgrind should be excluding the signals that it reserves for
> internal use when it does the mapping from the user requested mask to the
> mask that we
https://bugs.kde.org/show_bug.cgi?id=372504
Tom Hughes changed:
What|Removed |Added
CC||t...@compton.nu
--- Comment #21 from Tom Hughes -
https://bugs.kde.org/show_bug.cgi?id=372504
--- Comment #20 from Philippe Waroquiers ---
The below trace might show that the special signal (64) used by valgrind to
get a thread out of a syscall has been masked.
If that is the case, it should be relatively easy to write a reproducer:
* launch a t
https://bugs.kde.org/show_bug.cgi?id=372504
--- Comment #19 from David Hagood ---
OK, looking through the resulting trace file shows the following:
At startup, there's a lot of
10966 rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
10966 rt_sigprocmask(SIG_SETMASK, ~[], [], 8) = 0
Then, signal hand
https://bugs.kde.org/show_bug.cgi?id=372504
--- Comment #18 from Philippe Waroquiers ---
(In reply to David Hagood from comment #17)
> I would be happy to, if you or somebody else can tell me how.
strace -f -o vg.out valgrind
the file vg.out should contain all syscalls done by valgrind
and/or
https://bugs.kde.org/show_bug.cgi?id=372504
--- Comment #17 from David Hagood ---
I would be happy to, if you or somebody else can tell me how.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=372504
--- Comment #16 from Philippe Waroquiers ---
(In reply to David Hagood from comment #15)
> #1 0x380936a9 in do_syscall_for_client (syscall_mask=0x80ddebdb0,
> tst=0x80200c130, syscallno=130) at m_syswrap/syswrap-main.c:339
According to the
https://bugs.kde.org/show_bug.cgi?id=372504
--- Comment #15 from David Hagood ---
OK, the backtraces are:
#0 0x38056bf9 in do_syscall_WRK ()
#1 0x38056d52 in vgPlain_do_syscall (sysno=sysno@entry=39,
a1=a1@entry=0, a2=a2@entry=0, a3=a3@entry=0, a4=a4@entry=0,
a5=a5@ent
https://bugs.kde.org/show_bug.cgi?id=372504
--- Comment #14 from Philippe Waroquiers ---
(In reply to Philippe Waroquiers from comment #13)
> (In reply to David Hagood from comment #12)
> But even with an old gdb, you should be able to attach to the task
> you find in /proc//task
> and do backtr
https://bugs.kde.org/show_bug.cgi?id=372504
--- Comment #13 from Philippe Waroquiers ---
(In reply to David Hagood from comment #12)
> How recent is recent enough?
>
> GNU gdb (Ubuntu 7.7.1-0ubuntu5~14.04.2) 7.7.1
>
> And the trace really doesn't show any more than what I first posted: call to
https://bugs.kde.org/show_bug.cgi?id=372504
--- Comment #12 from David Hagood ---
How recent is recent enough?
GNU gdb (Ubuntu 7.7.1-0ubuntu5~14.04.2) 7.7.1
And the trace really doesn't show any more than what I first posted: call to
exit_group, then spin forever.
--
You are receiving this ma
https://bugs.kde.org/show_bug.cgi?id=372504
--- Comment #5 from David Hagood ---
OK, I've tried 3.11, with no change of behavior (still locks).
(gdb) p vgPlain_threads[1].status
$13 = VgTs_Yielding
(gdb) p vgPlain_threads[1].exitreason
$14 = VgSrc_None
(gdb) p vgPlain_threads[2].status
$15 = VgT
https://bugs.kde.org/show_bug.cgi?id=372504
--- Comment #11 from David Hagood ---
Created attachment 102262
--> https://bugs.kde.org/attachment.cgi?id=102262&action=edit
Trace of run with failure
Trace of run with lockup
--
You are receiving this mail because:
You are watching all bug change
https://bugs.kde.org/show_bug.cgi?id=372504
--- Comment #10 from Philippe Waroquiers ---
(In reply to Philippe Waroquiers from comment #9)
> (In reply to Philippe Waroquiers from comment #8)
> > (In reply to David Hagood from comment #6)
> > > BTW: When I say I see no other threads - that is I se
https://bugs.kde.org/show_bug.cgi?id=372504
--- Comment #9 from Philippe Waroquiers ---
(In reply to Philippe Waroquiers from comment #8)
> (In reply to David Hagood from comment #6)
> > BTW: When I say I see no other threads - that is I see no other threads
> > *within Valgrind itself* - I have
https://bugs.kde.org/show_bug.cgi?id=372504
--- Comment #8 from Philippe Waroquiers ---
(In reply to David Hagood from comment #6)
> BTW: When I say I see no other threads - that is I see no other threads
> *within Valgrind itself* - I have not attached to the process running under
> Valgrind.
I
https://bugs.kde.org/show_bug.cgi?id=372504
--- Comment #7 from Philippe Waroquiers ---
(In reply to David Hagood from comment #5)
> OK, I've tried 3.11, with no change of behavior (still locks).
>
> (gdb) p vgPlain_threads[1].status
> $13 = VgTs_Yielding
> (gdb) p vgPlain_threads[1].exitreason
https://bugs.kde.org/show_bug.cgi?id=372504
--- Comment #6 from David Hagood ---
BTW: When I say I see no other threads - that is I see no other threads *within
Valgrind itself* - I have not attached to the process running under Valgrind.
--
You are receiving this mail because:
You are watching
https://bugs.kde.org/show_bug.cgi?id=372504
--- Comment #4 from Philippe Waroquiers ---
(In reply to David Hagood from comment #3)
> I tried with the version of Valgrind delivered with Ubuntu 14.04 (3.9), and
> had the problem (hence why I went to 3.12). If you think it's worth it, I am
> willing
https://bugs.kde.org/show_bug.cgi?id=372504
--- Comment #3 from David Hagood ---
I tried with the version of Valgrind delivered with Ubuntu 14.04 (3.9), and had
the problem (hence why I went to 3.12). If you think it's worth it, I am
willing to try 3.11 - I couldn't see any sources for download,
https://bugs.kde.org/show_bug.cgi?id=372504
--- Comment #2 from Philippe Waroquiers ---
(In reply to Philippe Waroquiers from comment #1)
> But 361615 was (recently) fixed in 3.12, and touches the thread termination.
I meant bug 361615
--
You are receiving this mail because:
You are watching
https://bugs.kde.org/show_bug.cgi?id=372504
Philippe Waroquiers changed:
What|Removed |Added
CC||philippe.waroquiers@skynet.
26 matches
Mail list logo
