[Bug 59187] New: Page fault on write access from ntdll -- WIRES-X radio internet linking software
http://bugs.winehq.org/show_bug.cgi?id=59187 Bug ID: 59187 Summary: Page fault on write access from ntdll -- WIRES-X radio internet linking software Product: Wine Version: 11.0-rc4 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: ntdll Assignee: wine-bugs@list.winehq.org Reporter: chrism0dwk@gmail.com Distribution: --- Created attachment 80050 --> http://bugs.winehq.org/attachment.cgi?id=80050 Backtrace and terminal output Hi, I have an issue running an old piece of 32-bit Windows software, WIRES-X (Yaesu Musen, https://www.yaesu.com/jp/en/wires-x/index.php). The software enables radio transceivers to be linked via the internet to create wide-area coverage two-way radio communications. Hence the important features of the software are: internet connectivity, two-way radio connectivity via COM port, and system audio (allowing the user to monitor radio traffic through the computer speakers). The platform is Mint 22.2 (6.14.0-37-generic), with Wine 11.0-rc4. Since the software is 32-bit, I am running a 32-bit Wine PREFIX. To get the WIRES-X internet connectivity running, I had to also install wininet via winetricks. The problem is that the WIRES-X software crashes when the radio detects an incoming signal. This obviously doesn't happen if the software is running natively under Windows, so seems to be a Wine bug. I have attached both the backtrace provided by Wine, and also the terminal output including the command I ran to launch the software. Without any technical Wine knowledge, I'm having difficulty understanding the backtrace, but am guessing the fault lies in the ntdll.dll module. Any ideas what might be going wrong? Thanks, Chris -- 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=59187 --- Comment #2 from Chris Jewell <chrism0dwk@gmail.com> --- Created attachment 80054 --> http://bugs.winehq.org/attachment.cgi?id=80054 Terminal stderr log with WINEDEBUG=+server,+pid,+timestamp,+comm,+file,+seh -- 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=59187 --- Comment #3 from Chris Jewell <chrism0dwk@gmail.com> --- (In reply to Zeb Figura from comment #1)
Can you please attach a log with WINEDEBUG=+server,+pid,+timestamp,+comm,+file,+seh ?
Thanks Zeb, see linked attachment. -- 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=59187 Chris Jewell <chrism0dwk@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Distribution|--- |Mint CC| |chrism0dwk@gmail.com -- 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=59187 Zeb Figura <z.figura12@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |z.figura12@gmail.com --- Comment #1 from Zeb Figura <z.figura12@gmail.com> --- Can you please attach a log with WINEDEBUG=+server,+pid,+timestamp,+comm,+file,+seh ? -- 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=59187 Chris Jewell <chrism0dwk@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #80054|0 |1 is obsolete| | --- Comment #4 from Chris Jewell <chrism0dwk@gmail.com> --- Created attachment 80107 --> http://bugs.winehq.org/attachment.cgi?id=80107 Updated: Terminal stderr log with WINEDEBUG=+server,+pid,+timestamp,+comm,+file,+seh This log provides a more solid link to the detailed log output requested. -- 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=59187 --- Comment #5 from Chris Jewell <chrism0dwk@gmail.com> --- @Zeb Figura -- apologies, a colleague notified me that we had a server problem with the original link to the detailed log output. I've replaced this link with something different. Chris -- 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=59187 --- Comment #6 from Zeb Figura <z.figura12@gmail.com> --- Whatever's going wrong doesn't seem to clearly be directly related to the serial code unfortunately. This one is going to be hard to debug. -- 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=59187 --- Comment #7 from Chris Jewell <chrism0dwk@gmail.com> --- Yes, it feels like it may not be the serial communication that is at fault. There is a diagnostics tool in the software allowing the radio audio level to be set. This appears to communicate with the radio fine, switching it into transmit without problem. The software does communicate with the computer's sound system, essentially using the computer speakers instead of the radio's speakers. I wonder if it could be something to do with that. -- 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=59187 --- Comment #8 from Chris Jewell <chrism0dwk@gmail.com> --- This is interesting. Using `winecfg`, I changed my Audio Output Device to be explicit ("Meteor Lake-P HD Audio Controller Speakers") as opposed to "(System Default)". The resulting backtrace shows a different address for the exception (0x006904f5), as shown in the new attachment "Backtrace with explicit audio output device". Might this point to a soundcard problem, I wonder? -- 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=59187 --- Comment #9 from Chris Jewell <chrism0dwk@gmail.com> --- Created attachment 80196 --> http://bugs.winehq.org/attachment.cgi?id=80196 Backtrace with explicit audio output device Compare this backtrace with the previous backtrace in 80050. The error location is different. -- 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=59187 --- Comment #10 from Zeb Figura <z.figura12@gmail.com> --- Hmm, try adding +mmdevapi,+pulse,+alsa,+dsound,+xaudio2,+quartz,warn+all then? -- 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=59187 Chris Jewell <chrism0dwk@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #80107|0 |1 is obsolete| | --- Comment #11 from Chris Jewell <chrism0dwk@gmail.com> --- Created attachment 80308 --> http://bugs.winehq.org/attachment.cgi?id=80308 Terminal stderr log with +mmdevapi,+pulse,+alsa,+dsound,+xaudio2,+quartz,warn+all Note that this is with a slightly updated Wine 11.1 (retrieved from WineHQ Ubuntu repo). This shows a segfault apparently emanating from mmdevapi. -- 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 (1)
-
WineHQ Bugzilla