http://bugs.winehq.org/show_bug.cgi?id=22629 --- Comment #27 from Vincent Pelletier <plr.vincent(a)gmail.com> 2010-05-14 17:33:16 --- (In reply to comment #26)
ok i ad julliard(a)winehq.org to the cc list he sould fix or remove his 2f3fa8596bc6410a3b535e2f12bf551841334ad7 patch
Thanks a lot for running this regression test and identifying the "bad" commit. I just read the diff (and the file to get a bit more context) and I don't see where the problem could be. So I tend to think this is in fact a kernel (or libc ?) bug: - gcc doesn't identify segfault source, stack itself seems broken after the segfault - it works for some people, not for others (I guess we need more details, as kernel version & distro patches, libc & distro patches, multi/single core, etc to find a common denominator). Personally, I use Debian Sid kernel (2.6.32-based) and their libc (eglibc IIRC) on AMD64 dual core on one socket. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email 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.