http://bugs.winehq.org/show_bug.cgi?id=24359
Summary: dbghelp doesn't support DW_LNE_set_discriminator (gcc 4.6) Product: Wine Version: 1.3.2 Platform: x86-64 OS/Version: Linux Status: NEW Keywords: download, source Severity: enhancement Priority: P2 Component: dbghelp AssignedTo: wine-bugs@winehq.org ReportedBy: austinenglish@gmail.com CC: eric.pouech@orange.fr Depends on: 23137
This is part two of bug 23137.
With new gcc (4.6), a crash in wine shows: fixme:dbghelp:elf_new_wine_thunks Duplicate in L"kernel32<elf>": __wine_dbch_time<7ef001c0-00000010> __dbch<7ef001c0-0> fixme:dbghelp:elf_new_wine_thunks Duplicate in L"kernel32<elf>": __wine_dbch_ver<7ef001e0-00000010> __dbch<7ef001e0-0>
in terminal several times.
http://bugs.winehq.org/show_bug.cgi?id=24359
Bug 24359 depends on bug 23137, which changed state.
Bug 23137 Summary: dbghelp doesn't support DW_LNE_set_discriminator (gcc 4.6) http://bugs.winehq.org/show_bug.cgi?id=23137
What |Old Value |New Value ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED
http://bugs.winehq.org/show_bug.cgi?id=24359
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|dbghelp doesn't support |dbghelp has lots of |DW_LNE_set_discriminator |'elf_new_wine_thunks |(gcc 4.6) |Duplicate' (gcc 4.6)
http://bugs.winehq.org/show_bug.cgi?id=24359
--- Comment #1 from Eric Pouech eric.pouech@orange.fr 2011-04-08 04:28:27 CDT --- should be fixed by now please retest
http://bugs.winehq.org/show_bug.cgi?id=24359
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED
--- Comment #2 from Austin English austinenglish@gmail.com 2011-04-11 01:17:31 CDT --- With 6eed4c4241ae30f9e0af2581555c5ce6c25623f3, I get: austin@aw21 ~/wine-git/dlls/kernel32/tests $ make debugger.ok ../../../tools/runtest -q -P wine -M kernel32.dll -T ../../.. -p kernel32_test.exe.so debugger.c && touch debugger.ok fixme:iphlpapi:NotifyAddrChange (Handle 0xb2e91c, overlapped 0xb2e900): stub wine: configuration in '/home/austin/.wine' has been updated. wine: Unhandled page fault on write access to 0x00000000 at address 0x685e13d8 (thread 0035), starting debugger... winedbg: Internal crash at 0x68631aa4 debugger.c:412: Test failed: exit code = c0000354 debugger.c:480: Tests skipped: "none" debugger test needs user interaction wine: Unhandled page fault on write access to 0x00000000 at address 0x685e13d8 (thread 0039), starting debugger... wine: Unhandled page fault on write access to 0x00000000 at address 0x685e13d8 (thread 003d), starting debugger... wine: Unhandled page fault on write access to 0x00000000 at address 0x685e13d8 (thread 0041), starting debugger... wine: Unhandled page fault on write access to 0x00000000 at address 0x685e13d8 (thread 0045), starting debugger... make: *** [debugger.ok] Error 1
so the spam is fixed, though that internal crash seems nasty...
austin@aw21 ~/wine-git/dlls/kernel32/tests $ /opt/gcc-4.6/bin/gcc --version gcc (GCC) 4.6.0 Copyright (C) 2011 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
http://bugs.winehq.org/show_bug.cgi?id=24359
--- Comment #3 from Eric Pouech eric.pouech@orange.fr 2011-04-11 06:04:52 CDT --- does winedbg on a test app (like winemine) shows the same issue ? if so, what's the output of winedbg --gdb winedbg winemine (using gdb to get a backtrace of failing winedbg)
A+
http://bugs.winehq.org/show_bug.cgi?id=24359
--- Comment #4 from Austin English austinenglish@gmail.com 2011-04-11 11:37:58 CDT --- (In reply to comment #3)
does winedbg on a test app (like winemine) shows the same issue ? if so, what's the output of winedbg --gdb winedbg winemine (using gdb to get a backtrace of failing winedbg)
If I do: $ wine winedbg winemine with wine installed it /usr/local, works fine, but doing: $ ./loader/wine winedbg winemine WineDbg starting on pid 002e winedbg: Internal crash at 0x7eefd19c
Adding --gdb doesn't help much: 002e:002f: create process 'C:\windows\system32\winemine.exe'/0x110738 @0x7ef78800 (0<0>) winedbg: Internal crash at 0x7eef519c
doesn't seem limited to 4.6.0 though, I get the same with 4.4.5. Weird..
http://bugs.winehq.org/show_bug.cgi?id=24359
--- Comment #5 from Austin English austinenglish@gmail.com 2011-04-11 12:04:59 CDT --- (In reply to comment #4)
(In reply to comment #3)
does winedbg on a test app (like winemine) shows the same issue ? if so, what's the output of winedbg --gdb winedbg winemine (using gdb to get a backtrace of failing winedbg)
If I do: $ wine winedbg winemine with wine installed it /usr/local, works fine, but doing: $ ./loader/wine winedbg winemine WineDbg starting on pid 002e winedbg: Internal crash at 0x7eefd19c
Adding --gdb doesn't help much: 002e:002f: create process 'C:\windows\system32\winemine.exe'/0x110738 @0x7ef78800 (0<0>) winedbg: Internal crash at 0x7eef519c
doesn't seem limited to 4.6.0 though, I get the same with 4.4.5. Weird..
Ignore, bad patch in my tree, sorry for the noise.
http://bugs.winehq.org/show_bug.cgi?id=24359
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #6 from Alexandre Julliard julliard@winehq.org 2011-04-15 12:51:05 CDT --- Closing bugs fixed in 1.3.18.