[Bug 38481] New: d2d1/tests/d2d1.c crashes when running under valgrind
https://bugs.winehq.org/show_bug.cgi?id=38481 Bug ID: 38481 Summary: d2d1/tests/d2d1.c crashes when running under valgrind Product: Wine Version: 1.7.41 Hardware: x86 OS: Linux Status: NEW Keywords: download, source, testcase, valgrind Severity: normal Priority: P2 Component: d2d Assignee: wine-bugs(a)winehq.org Reporter: austinenglish(a)gmail.com Distribution: Debian Created attachment 51323 --> https://bugs.winehq.org/attachment.cgi?id=51323 output/backtrace fixme:d3d_shader:shader_sm4_read_instruction Unrecognized opcode 0x5a, opcode_token 0x0300005a. fixme:d3d_shader:shader_sm4_read_instruction Unrecognized opcode 0x64, opcode_token 0x04002064. fixme:d3d_shader:shader_sm4_read_instruction Unrecognized opcode 0x65, opcode_token 0x03000065. fixme:d3d_shader:shader_sm4_read_instruction Unrecognized opcode 0x68, opcode_token 0x02000068. fixme:d3d_shader:shader_sm4_read_src_param Unhandled swizzle type 0. fixme:dwrite:dwritefactory_CreateMonitorRenderingParams (0x1): monitor setting ignored wine: Unhandled page fault on read access to 0x09e8a080 at address 0x52c3b80 (thread 0031), starting debugger... preloader: Warning: failed to reserve range 00110000-68000000 Unhandled exception: page fault on read access to 0x09e8a080 in 32-bit code (0x052c3b80). Backtrace: =>0 0x052c3b80 (0x06716640) 1 0x0c244c8b (0x0424448b) 2 0x24448b24 (0x0489f219) 0x052c3b80: pushl %ebp Modules: Module Address Debug info Name (70 modules) ELF 4000000- 4021000 Deferred ld-linux.so.2 ELF 4023000- 4025000 Deferred vgpreload_core-x86-linux.so ELF 4025000- 4034000 Deferred vgpreload_memcheck-x86-linux.so ELF 4035000- 41ec000 Dwarf libwine.so.1 ELF 41ec000- 4207000 Deferred d2d1_test<elf> \-PE 41f0000- 4207000 \ d2d1_test -- 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.
https://bugs.winehq.org/show_bug.cgi?id=38481 --- Comment #1 from Henri Verbeet <hverbeet(a)gmail.com> --- I'm afraid the backtrace isn't very helpful for finding the cause, and I can't reproduce this myself. The address 0x052c3b80 is close enough to libnvidia-tls.so.340.65 that it might somehow be graphics driver related though. The debug messages suggest it crashes either in test_state_block() or at the start of test_color_brush(). -- 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.
https://bugs.winehq.org/show_bug.cgi?id=38481 --- Comment #2 from Austin English <austinenglish(a)gmail.com> --- (In reply to Henri Verbeet from comment #1)
I'm afraid the backtrace isn't very helpful for finding the cause, and I can't reproduce this myself. The address 0x052c3b80 is close enough to libnvidia-tls.so.340.65 that it might somehow be graphics driver related though. The debug messages suggest it crashes either in test_state_block() or at the start of test_color_brush().
I tried only enabling one test at a time, but then the issue wasn't reproducible. Adding some debugging statements, it's in test_color_brush(), when creating the device: if (!(device = create_device())) { skip("Failed to create device, skipping tests.\n"); return; } -- 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.
https://bugs.winehq.org/show_bug.cgi?id=38481 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |UPSTREAM --- Comment #3 from Austin English <austinenglish(a)gmail.com> --- (In reply to Henri Verbeet from comment #1)
I'm afraid the backtrace isn't very helpful for finding the cause, and I can't reproduce this myself. The address 0x052c3b80 is close enough to libnvidia-tls.so.340.65 that it might somehow be graphics driver related though. The debug messages suggest it crashes either in test_state_block() or at the start of test_color_brush().
I can't reproduce on intel/mesa either, so marking as upstream. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=38481 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #4 from Austin English <austinenglish(a)gmail.com> --- Closing. -- 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.
https://bugs.winehq.org/show_bug.cgi?id=38481 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |RESOLVED --- Comment #5 from Austin English <austinenglish(a)gmail.com> --- This was inadvertently caught up in my unclosed bugs filter. NOTOURBUG should only be closed when fixed upstream. Setting back to RESOLVED NOTOURBUG. Sorry for the spam. -- 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.
http://bugs.winehq.org/show_bug.cgi?id=38481 --- Comment #6 from Hans Leidekker <hans@meelstraat.net> --- (In reply to Austin English from comment #5)
This was inadvertently caught up in my unclosed bugs filter. NOTOURBUG should only be closed when fixed upstream.
Setting back to RESOLVED NOTOURBUG.
Can we close this bug now that we're no longer triaging valgrind reports? -- 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.
http://bugs.winehq.org/show_bug.cgi?id=38481 Austin English <austinenglish@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|NOTOURBUG |ABANDONED Status|RESOLVED |CLOSED --- Comment #7 from Austin English <austinenglish@gmail.com> --- Sure -- 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.
participants (2)
-
wine-bugs＠winehq.org -
WineHQ Bugzilla