http://bugs.winehq.org/show_bug.cgi?id=24193
--- Comment #5 from Jerome Leclanche adys.wh@gmail.com 2010-09-12 05:40:58 CDT --- (In reply to comment #3)
I don't think setting /proc/sys/kernel/yama/ptrace_scope is a viable workaround
let's consider three regular cases of wine usage: A/ a program crashes, and default fault handler starts winedbg on this process B/ a program sets its own stack unwinder (likely in a fault handler) C/ a programmer fires winedbg foo
I didn't analyse anything just yet but it just hit me that the crash-on-login is likely due to warden looking around the game.
Seeing as Warden is a different process than wow; with your solution, it would have the same grandparent (wineserver), but would it be looking at WoW's memory (a sister process) or wineserver's memory? Wouldn't it still crash if it looked at WoW's memory?