[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 114564] clone() and stacks
From:       Samuel Thibault <samuel.thibault () ens-lyon ! org>
Date:       2005-10-17 13:55:05
Message-ID: 20051017135505.17970.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
         
http://bugs.kde.org/show_bug.cgi?id=114564         




------- Additional Comments From samuel.thibault ens-lyon org  2005-10-17 15:55 \
------- Hi,

Tom Hughes, le Mon 17 Oct 2005 13:43:07 -0000, a écrit :
> If we switch when pushing a signal frame shouldn't we switch back again when we pop \
> it?


Hm, iirc, the pop is performed by the guest RET instruction, so the
switch back is detected there.

> Doesn't the one in VG_(set_running) take care of that anyway? Presumably that is \
> (or should be called) when we start running the signal handler in the other thread?


Oh, indeed.

While debugging, I added the stack switch in set_running _after_ having
added the one in the frame push, that's why I actually added both, but
the one in m_signals.c seems redundant indeed, the applications that I'm
testing do work fine with only the one in VG_(set_running).

Regards,
Samuel


[prev in list] [next in list] [prev in thread] [next in thread]