http://bugs.winehq.org/show_bug.cgi?id=59333 --- Comment #9 from Hoshino Lina <lina@lina.yt> --- I was thinking about the "masking" USR1 and... I guess I was confused about the meaning. Since USR1 is just a normally handled signal, I guess it would be sufficient to just check if %rip is inside the syscall dispatcher and just set a flag and return? Then the syscall handler itself can check the flag, and if set, jump to the rest of the USR1 handling code. You'd need some subtlety around "carving out" the check itself so it would go something like: - Between start of __wine_syscall_dispatcher and loading the flag, do the above - After the flag is loaded, and before jumping into the syscall, just handle it normally in the signal handler (considered "in syscall"). - If it's after syscall return and back in __wine_syscall_dispatcher, perhaps the easiest thing to do is just have the USR1 handler alter the signal return context to restart the syscall return path (you'd have to ensure the syscall return code is idempotent with respect to user state). This only really matters if the context is allowed to be modified by another thread "during" a syscall. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.