[Bug 50092] New: Version 1.00 of Vellum's DrawingBoard works well, but crashes when a straight line is drawn
https://bugs.winehq.org/show_bug.cgi?id=50092
Bug ID: 50092 Summary: Version 1.00 of Vellum's DrawingBoard works well, but crashes when a straight line is drawn Product: Wine Version: 5.20 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: major Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: dodgy@ntlworld.com Distribution: ---
Created attachment 68562 --> https://bugs.winehq.org/attachment.cgi?id=68562 Vellum DrawingBoard V1.00 crashes when straight line drawn
Vellum's DrawingBoard package is an early (Windows 3.1/DOS) technical drawing package. It no longer runs on Windows after XP, and would be very expensive to replace! It runs very well with Ubuntu under WINE, except for the following major issue:
When drawing a straight line using the 'elastic band' icon, the program crashes as soon as the initial start point is specified by a mouse click. Occasionally it does not, and several lines may be drawn, but it will usually crash before less than 10 are drawn. An inability to draw lines is a major problem for a drafting package. I have tested most other commands, and so far everything works except this one failing.
https://bugs.winehq.org/show_bug.cgi?id=50092
Zebediah Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |win16 Severity|major |normal CC| |z.figura12@gmail.com
--- Comment #1 from Zebediah Figura z.figura12@gmail.com --- Can you please attach a log with WINEDEBUG=+relay,+seh,+int?
https://bugs.winehq.org/show_bug.cgi?id=50092
--- Comment #2 from Dodgy dodgy@ntlworld.com --- I am a linux newbie - finding it very hard to manipulate the command-line language.
I assume that you require me to run a command from the terminal like:
WINEDEBUG=+relay,+seh,+int dwgboard.exe
I have two problems with this:
1 - the winedebug command cannot find dwgboard.exe, and I do not know how to specify a full hierarchical name
2 - if I can get this command to run, I assume that it will create a log file. But I do not know the name of this, or where it will be placed...
I shall work on trying to run the command....
DG
https://bugs.winehq.org/show_bug.cgi?id=50092
--- Comment #3 from Zebediah Figura z.figura12@gmail.com --- See https://wiki.winehq.org/FAQ#How_can_I_get_a_debugging_log_.28a.k.a._terminal_output.29.3F for instructions. Sorry, I should have linked that in the first place...
https://bugs.winehq.org/show_bug.cgi?id=50092
--- Comment #4 from Dodgy dodgy@ntlworld.com --- Created attachment 68571 --> https://bugs.winehq.org/attachment.cgi?id=68571 I hope this is the windebug log of a crash of Vellums DrawingBoard V1.0
Only 32 bytes - not sure if this will be useful.
https://bugs.winehq.org/show_bug.cgi?id=50092
--- Comment #5 from Dodgy dodgy@ntlworld.com --- Created attachment 68572 --> https://bugs.winehq.org/attachment.cgi?id=68572 Longer log file of Vellum DrawingBoard V1.0 crashing
https://bugs.winehq.org/show_bug.cgi?id=50092
--- Comment #6 from Zebediah Figura z.figura12@gmail.com --- You need to run "wine DWGBOARD.EXE", not just the program name.
https://bugs.winehq.org/show_bug.cgi?id=50092
--- Comment #7 from Dodgy dodgy@ntlworld.com --- Thanks - it is that level of support that I need!
Is it the case that WINEDEBUG prog-name will actually run 'prog-name', or do I have to say:
WINEDEBUG WINE prog-name &> log-file
to run the program with debug turned on and with output to the log file?
https://bugs.winehq.org/show_bug.cgi?id=50092
--- Comment #8 from Zebediah Figura z.figura12@gmail.com --- The full command should be "WINEDEBUG=+relay,+seh,+int wine prog-name &> log-file". You need to set the environment variable on the same line (otherwise it'll have no effect), and "wine" should be in lowercase, or else be the path to the "wine" executable installed on your system.
https://bugs.winehq.org/show_bug.cgi?id=50092
--- Comment #9 from Dodgy dodgy@ntlworld.com --- Thanks!
I have run that command - it worked, and brought up the cad package. The first command I did was 'draw a line' and it crashed at that point. So everything seemed OK.
Problem was, the log file was 102Mb in size. I ran the process again - the log file was 110Mb. Is this an expected size? If it is I can put it on the web and publish a URL to it, but I though I had better check first...
https://bugs.winehq.org/show_bug.cgi?id=50092
--- Comment #10 from Zebediah Figura z.figura12@gmail.com --- (In reply to Dodgy from comment #9)
Thanks!
I have run that command - it worked, and brought up the cad package. The first command I did was 'draw a line' and it crashed at that point. So everything seemed OK.
Problem was, the log file was 102Mb in size. I ran the process again - the log file was 110Mb. Is this an expected size? If it is I can put it on the web and publish a URL to it, but I though I had better check first...
Yes, that's expected. Usually compression (e.g. gzip) will bring it down to below 10 MB, at which point it can be attached here.
https://bugs.winehq.org/show_bug.cgi?id=50092
--- Comment #11 from Dodgy dodgy@ntlworld.com --- Created attachment 68588 --> https://bugs.winehq.org/attachment.cgi?id=68588 compressed log of Vellum Drawingboard v1.0 dump
https://bugs.winehq.org/show_bug.cgi?id=50092
--- Comment #12 from Dodgy dodgy@ntlworld.com --- Thanks for being so patient - hope it's worth it!
https://bugs.winehq.org/show_bug.cgi?id=50092
--- Comment #13 from Zebediah Figura z.figura12@gmail.com --- Unfortunately I didn't see the clues I was hoping for [not any fault of yours, the log was correct].
There's no place where I can download the program for debugging, is there?
It's very clearly reading past the end of a segment; based on the faulting instruction I'd guess it's doing something like strchr(buffer, '['), but I can't tell if the buffer is ever written to past the initial module load, and I have no idea what it's supposed to contain. I'd honestly guess DDE, just because of the bracket, but there doesn't seem to be any DDE involved.
https://bugs.winehq.org/show_bug.cgi?id=50092
--- Comment #14 from Dodgy dodgy@ntlworld.com --- "...There's no place where I can download the program for debugging, is there?.."
Very unlikely! It's abandonware from some time in the 1980s, I believe. I downloaded my copy from a university site, but that was long ago and I can't see anything out on the web now.
I can put a copy up on a URL if you don't mind waiting for a day or so. But the whole program is only about 10Mb, so I could zip it and put it on here as an attachment if you want...
https://bugs.winehq.org/show_bug.cgi?id=50092
--- Comment #15 from Zebediah Figura z.figura12@gmail.com --- We can't host copyrighted binaries here, even if they are abandonware, but if you can upload it elsewhere, or even send it directly to my mail address, that might be workable...
https://bugs.winehq.org/show_bug.cgi?id=50092
--- Comment #16 from Dodgy dodgy@ntlworld.com --- Your emailer rejected my message with a zipped attachment as potentially malicious. I will put the file up on one of my webservers. Stay tuned...
https://bugs.winehq.org/show_bug.cgi?id=50092
--- Comment #17 from Dodgy dodgy@ntlworld.com --- DWGboard now available at http://eezebilt.tk/download.html
https://bugs.winehq.org/show_bug.cgi?id=50092
--- Comment #18 from Dodgy dodgy@ntlworld.com --- Hi - would appreciate knowing when you no longer need the download page, as I would like to remove it from the server at some point...
https://bugs.winehq.org/show_bug.cgi?id=50092
--- Comment #19 from Zebediah Figura z.figura12@gmail.com --- (In reply to Dodgy from comment #18)
Hi - would appreciate knowing when you no longer need the download page, as I would like to remove it from the server at some point...
I have the program locally now, thanks, although I haven't been able to find the bug yet. It's more than a little difficult...
https://bugs.winehq.org/show_bug.cgi?id=50092
--- Comment #20 from Dodgy dodgy@ntlworld.com --- I don't know if this bug is still being investigated, but I have a bit more information about when it happens.
I am using Ubuntu 20.04.2 and Wine 6.1 (dev) Drawingboard is V1.00
This is a CAD package, which allows a user to draw various shapes using a mouse. It crashes when a specific mouse command is made. This is a specific command to draw a straight line.
There are several straight line input commands available - draw point-to-point, draw parallel lines, etc. The problem occurs with the 'rubber band' command. This is the standard command to use where two points are specified and a line is drawn between them.
If this command is used by clicking on a start point, releasing the click, moving the mouse and then clicking on the end point, the command works fine.
If this command is used by clicking on a prespecified point (a corner of an existing square, for instance), then dragging the mouse to an end point and releasing the click, the command works fine.
If this command is used by clicking on a part of the drawing which is not yet specified as the start of a line, then dragging the mouse to an end point, the application crashes the moment the cursor is dragged away from the start point.
So the problem seems to be associated with specifying the start of a mouse position...
https://bugs.winehq.org/show_bug.cgi?id=50092
--- Comment #21 from Zebediah Figura z.figura12@gmail.com --- Yeah, I'm sorry, I haven't looked at this in a while. It was proving very difficult to debug.
If I get some time this weekend I'll try to give it another shot.
https://bugs.winehq.org/show_bug.cgi?id=50092
--- Comment #22 from Dodgy dodgy@ntlworld.com --- Kind of you to come back! I'm able to use the program in a crippled mode, so it's not critical for me - but every so often I forget to avoid the problem and crash the application :( Still, so long as I save frequently...
https://bugs.winehq.org/show_bug.cgi?id=50092
Roman Pišl rpisl@seznam.cz changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |rpisl@seznam.cz
--- Comment #23 from Roman Pišl rpisl@seznam.cz --- I came across this while trying to run another Win16 CAD software for my colleague and there is one good news: this bug does not occur with otvdm (https://github.com/otya128/winevdm). So you have three options: run the software on Windows, find and port the needed or all modifications from otvdm into Wine or run otvdm in Wine. Unfortunately running otvdm in vanilla Wine is not possible and two hacks are required.
https://bugs.winehq.org/show_bug.cgi?id=50092
--- Comment #24 from Roman Pišl rpisl@seznam.cz --- Instructions how to run DrawingBoard with a tested version of otvdm in Wine can be found in bug 51224.
https://bugs.winehq.org/show_bug.cgi?id=50092
--- Comment #25 from Roman Pišl rpisl@seznam.cz --- Created attachment 70157 --> https://bugs.winehq.org/attachment.cgi?id=70157 Patch
Bisected this is fixed by this commit: https://github.com/otya128/winevdm/commit/c7e373b0f84e1c2c0c6a5cbb44321ea8d9...
I'm attaching a fix for current Wine. However this fix has some magic numbers and also I'm not sure how to proceed with submitting foreign patches.
https://bugs.winehq.org/show_bug.cgi?id=50092
Julian Rüger jr98@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jr98@gmx.net
https://bugs.winehq.org/show_bug.cgi?id=50092
--- Comment #26 from Dodgy dodgy@ntlworld.com --- Thanks very much for the response - sorry I haven't been following this closely. I will try to understand and apply the workround - it was getting very frustrating doing a complex drawing and then having the application crash before I had saved it!
https://bugs.winehq.org/show_bug.cgi?id=50092
--- Comment #27 from Roman Pišl rpisl@seznam.cz --- Please add the patch keyword.
https://bugs.winehq.org/show_bug.cgi?id=50092
Zebediah Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |patch
-
WineHQ Bugzilla