[Bug 54890] New: Ultimate Doom Builder will crash if some dialoge boxes are used
https://bugs.winehq.org/show_bug.cgi?id=54890 Bug ID: 54890 Summary: Ultimate Doom Builder will crash if some dialoge boxes are used Product: Wine Version: 8.6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: beneschork(a)gmail.com Distribution: --- Created attachment 74388 --> https://bugs.winehq.org/attachment.cgi?id=74388 Crash log Whenever I use Ultimate doom Builder, I will often need to change a Thing* ID or a texture. To do this, I have to click on the linedef or thing to open its dialog box. There are fields I use to enter a string for the texture name or and integer for the TID, and whenever I do, wine immediately throws up an error and I have to save the crash log. This bug is replaceable on my machine, I have even changed distros. -- 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=54890 --- Comment #1 from Edvan <beneschork(a)gmail.com> --- In doom, a Thing is any actor that isn't level geometry. I should say that the bug is CONSISTENTLY replaceable on my machine. -- 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=54890 --- Comment #2 from Rafał Mużyło <galtgendo(a)o2.pl> --- Attach full output, not just the backtrace. (though it would be a bit hilarious if this ends up being effectively a dupe of a certain bug...) -- 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=54890 Zeb Figura <z.figura12(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Component|-unknown |mscoree Keywords| |download, source Severity|major |normal --- Comment #3 from Zeb Figura <z.figura12(a)gmail.com> --- It crashes in libmono, trying to call wcslen() on a junk pointer. Looks like source is available here: <https://github.com/jewalky/UltimateDoomBuilder> -- 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=54890 --- Comment #4 from Edvan <beneschork(a)gmail.com> --- (In reply to Rafał Mużyło from comment #2)
Attach full output, not just the backtrace. (though it would be a bit hilarious if this ends up being effectively a dupe of a certain bug...)
How do I do 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.
https://bugs.winehq.org/show_bug.cgi?id=54890 Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |o.dierick(a)piezo-forte.be --- Comment #5 from Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> --- (In reply to Edvan from comment #4)
(In reply to Rafał Mużyło from comment #2)
Attach full output, not just the backtrace. (though it would be a bit hilarious if this ends up being effectively a dupe of a certain bug...)
How do I do that?
Hello, Instructions to get a log can be found there: https://wiki.winehq.org/FAQ#get_log Regards. -- 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=54890 --- Comment #6 from Edvan <beneschork(a)gmail.com> --- Created attachment 74420 --> https://bugs.winehq.org/attachment.cgi?id=74420 log.txt -- 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=54890 --- Comment #7 from Edvan <beneschork(a)gmail.com> --- It took me a while, but I did get logging to work. When I followed the guide I also got output.txt, which is 7.1 Gigabytes in size. -- 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=54890 --- Comment #8 from Rafał Mużyło <galtgendo(a)o2.pl> --- ...log.txt will likely suffice... Having said that,... That last line before stacktrace may matter... Get the log again, this time with WINEDEBUG='ole,shell'. -- 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=54890 --- Comment #9 from Edvan <beneschork(a)gmail.com> --- I ran the command like you said: "WINEDEBUG='ole,shell' wine <Then the location of the executable> >> /tmp/output.txt 2>&1" the output said it couldn't find an interpreter I then ran: "WINEDEBUG='ole,shell' +relay,+seh,+tid wine <Then the location of the executable> >> /tmp/output.txt 2>&1" That said it didn't know what +relay,+seh, and +tid meant. I got log.txt from running "wine <Then the location of the executable> &> /tmp/log.txt" -- 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=54890 --- Comment #10 from Olivier F. R. Dierick <o.dierick(a)piezo-forte.be> --- (In reply to Edvan from comment #9)
I then ran: "WINEDEBUG='ole,shell' +relay,+seh,+tid wine <Then the location of the executable> >> /tmp/output.txt 2>&1"
That said it didn't know what +relay,+seh, and +tid meant.
Hello, It fails because +relay,+seh,+tid must be added to the WINEDEBUG value which is a comma separated list. Remember to change directory first "cd <path to executable>" and then try: WINEDEBUG='ole,shell,+relay,+seh,+tid' wine Build.exe >> /tmp/output.txt 2>&1 Regards. -- 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=54890 --- Comment #11 from Rafał Mużyło <galtgendo(a)o2.pl> --- ... Personally, I prefer '2>&1 | tee foo.log' style, YMMV Also, in most cases, you don't want 'relay'. On a more general note, this reads as 'I don't get shell at all'. Well, while I wouldn't call myself anywhere near 'shell proficient'... What exactly did you type into the terminal in the first case and what *exactly* was the response ? -- 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=54890 --- Comment #12 from Edvan <beneschork(a)gmail.com> --- (In reply to Olivier F. R. Dierick from comment #10)
Remember to change directory first "cd <path to executable>" and then try: WINEDEBUG='ole,shell,+relay,+seh,+tid' wine Build.exe >> /tmp/output.txt 2>&1
Regards.
It did work, but output.txt is still 7 Gigabytes in size. Is it necessary for anyone to see it? -- 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=54890 --- Comment #13 from Edvan <beneschork(a)gmail.com> --- (In reply to Rafał Mużyło from comment #11)
What exactly did you type into the terminal in the first case and what *exactly* was the response ?
I ran "WINEDEBUG='ole,shell' wine /.wine/drive_c/users/sch/AppData/Local/Programs/'Ultimate Doom Builder'/Builder.exe >> /tmp/output.txt 2>&1" The reason I didn't cd into the 'Ultimate Doom Builder' directory is because when I have done that in the past I got an error telling me I needed wine mono. As it were, the first time I forgot to type 'wine' after 'ole,shell', a simple mistake to fix. So I did and output.txt is now 37,000 lines long. -- 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=54890 --- Comment #14 from Rafał Mużyło <galtgendo(a)o2.pl> --- At this point we're trying to see if the problem lies in SHAutoComplete being a stub or something less trivial to diagnose. -- 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=54890 --- Comment #15 from Edvan <beneschork(a)gmail.com> --- Thank you for your help, I really appreciate what wine has done for the community. -- 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=54890 --- Comment #16 from Edvan <beneschork(a)gmail.com> --- On an unrelated note, Doom Builder has an updater executable, and every time I run it, wine gives me an error saying I don't have Administrator access, does anyone know how to fix 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.
https://bugs.winehq.org/show_bug.cgi?id=54890 --- Comment #17 from Rafał Mużyło <galtgendo(a)o2.pl> --- If the error you're referring to is the one in 'public MainForm()' (from https://github.com/jewalky/UltimateDoomBuilder/blob/master/Source/Tools/Upda...), that 'bool CheckPremissions(string path)' looks like something that could hit an unimplemented path or two, though that's just a guess and I'm unsure which debug channels you should be checking to verify... Anything interesting in the common console output there ? -- 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=54890 --- Comment #18 from Edvan <beneschork(a)gmail.com> --- I didn't see anything realated to CheckPremissions() in the terminal output that I know of. The very last line of the terminal before I initiated the bug was: "00dc:fixme:uiautomation:UiaClientsAreListening ()" then wine said that I got an unknown while executing native code, and there may be something wrong with the mono runtime or the native libraries used by my application. Sorry for the delayed response. -- 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=54890 SpeedPermitting(a)gmail.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |SpeedPermitting(a)gmail.com --- Comment #19 from SpeedPermitting(a)gmail.com --- I can reproduce this same bug with Ultimate Doom Builder 3.0.0.4102 (efcce48) on Fedora Workstation 38 (6.4.15-200.fc38.x86_64) in wine-8.0.2 (stable) or wine-8.16 (devel). Should I add my console log output to this bug report, file my own report, or just monitor the status and test again if this bug is fixed in a future release? -- 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=54890 --- Comment #20 from Edvan <beneschork(a)gmail.com> --- (In reply to SpeedPermitting from comment #19)
I can reproduce this same bug with Ultimate Doom Builder 3.0.0.4102 (efcce48) on Fedora Workstation 38 (6.4.15-200.fc38.x86_64) in wine-8.0.2 (stable) or wine-8.16 (devel).
Should I add my console log output to this bug report, file my own report, or just monitor the status and test again if this bug is fixed in a future release?
I think you should just file a new bug report; this one was never resolved. -- 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=54890 Esme Povirk <madewokherd(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |madewokherd(a)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.
participants (1)
-
WineHQ Bugzilla