http://bugs.winehq.org/show_bug.cgi?id=31665
Bug #: 31665 Summary: Femap unexpected crash on rebuild database (or any command that involves it i.e. import) Product: Wine Version: 1.5.12 Platform: x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: dark.schneider@iol.it Classification: Unclassified
Created attachment 41633 --> http://bugs.winehq.org/attachment.cgi?id=41633 Backtrace of crash triggered by file->rebuild in femap 10.3 with wine 1.5.12
1) wine femap.exe 2) file->rebuild... 3) answer yes.
The crash happen with any action that implies a rebuild database by femap. I.e. if you import a "large" bdf, lunching a rebuild is just a fast way to check if the bug is present or not.
Wine version I tested without the bug (those are working): 1.0.1 1.1.29 1.3.6
Wine versions i tested with the bug (crash with similar backtrace to one attached): 1.4.1-2 (from debian repo) 1.5.6-2 (from debian repo) 1.5.12
I have tested with both femap 10.2 and femap 10.3 and they share the same problem with no difference (i.e. probably the code on their side did not changed and if someone has an older version around it may show the same bug). I have not tested Femap 10.3.1, but may show the same problem.
All of this is related to 32 bit version of femap and wine running on a AMD 64 bit system. I have no chance to test 32 bit on 32 bit.
The bug persist on another system with ati/amd video driver, tested with both open source and closed opposed by this system that has closed source nvidia blob. Due to this bug seems unrelated to the video rendering (e.g. the problem with femap not redrawing automatically the gl window looks unrelated, if needed I can post another bug for that, but it's minor glitch)
Best Regards, Gabriele Dini Ciacci
P.S. Unrelated practical thing that make it desirable to have a recent version of wine working: With 1.5.6-2 and 1.5.12 the program is much faster (especially on start-up and actually faster than on windows)
http://bugs.winehq.org/show_bug.cgi?id=31665
Gabriele Dini Ciacci dark.schneider@iol.it changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |dark.schneider@iol.it
http://bugs.winehq.org/show_bug.cgi?id=31665
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |regression
--- Comment #1 from Austin English austinenglish@gmail.com 2012-09-10 12:52:42 CDT --- Please run a regression test: http://wiki.winehq.org/RegressionTesting
http://bugs.winehq.org/show_bug.cgi?id=31665
Frédéric Delanoy frederic.delanoy@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |Abandoned? CC| |frederic.delanoy@gmail.com
--- Comment #2 from Frédéric Delanoy frederic.delanoy@gmail.com 2013-06-04 07:26:31 CDT --- Please retest with recent wine (1.5.31 or later) and run a regression test if the issue persists (http://wiki.winehq.org/RegressionTesting).
If you don't, this bug will be abandoned soon.
http://bugs.winehq.org/show_bug.cgi?id=31665
--- Comment #3 from Gabriele Dini Ciacci dark.schneider@iol.it 2013-06-04 16:03:24 CDT --- I just tested with 1.5.31 and (sadly) the problem persists.
With the current state of my system (64bit debian unstable) compiling wine is a bit ("bit" is an euphemism) problematic. I allocated to the task one 3 hour time slice a month ago and did not managed to get anything done. To my understanding the fastest way to compile wine would be to install a virtual machine running a 32bit system. I will perform this task the next time I have a long enough time slice.
I may more easily narrow the version that introduced the bug using pre-compiled wine versions, but I will not be able to find the exact commit by bisection. If someone takes the time to do the final part of the work, by locating the commit, I would be happy to do the first part by locating the the version that introduced the problem.
To sum up: - Bug in 1.5.31 persists. - Compiling on debian 64bit unstable is a bit a hassle (so regression test is quite hard to do for me). - I may locate the exact version, if useful, but someone would have to locate the commit then.
Best Regards, Gabriele Dini Ciacci
http://bugs.winehq.org/show_bug.cgi?id=31665
--- Comment #4 from Frédéric Delanoy frederic.delanoy@gmail.com 2013-06-06 07:34:14 CDT --- (In reply to comment #3)
I just tested with 1.5.31 and (sadly) the problem persists.
With the current state of my system (64bit debian unstable) compiling wine is a bit ("bit" is an euphemism) problematic. I allocated to the task one 3 hour time slice a month ago and did not managed to get anything done. To my understanding the fastest way to compile wine would be to install a virtual machine running a 32bit system. I will perform this task the next time I have a long enough time slice.
I may more easily narrow the version that introduced the bug using pre-compiled wine versions, but I will not be able to find the exact commit by bisection. If someone takes the time to do the final part of the work, by locating the commit, I would be happy to do the first part by locating the the version that introduced the problem.
To sum up:
- Bug in 1.5.31 persists.
- Compiling on debian 64bit unstable is a bit a hassle (so regression test is quite hard to do for me).
- I may locate the exact version, if useful, but someone would have to locate
the commit then.
Best Regards, Gabriele Dini Ciacci
http://wiki.winehq.org/WineOn64bit might help.
http://bugs.winehq.org/show_bug.cgi?id=31665
Michael Stefaniuc mstefani@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |mstefani@redhat.com
--- Comment #5 from Michael Stefaniuc mstefani@redhat.com 2013-06-10 16:36:11 CDT --- Can you please install the debugging symbols for Wine too and regenerate the backtrace? Without that the backtrace is kinda useless.
http://bugs.winehq.org/show_bug.cgi?id=31665
--- Comment #6 from Gabriele Dini Ciacci dark.schneider@iol.it 2013-06-22 08:05:25 CDT --- I had already read the guide for wine on 64 bits, but sadly it did not helped much in my case (naturally considering also the limited time factor). Thanks for the link anyway.
I include the back trace with debugging symbols installed (thanks for the tip, i was stupid to not do that at first). They are for version 1.4.1 of wine, since this is a production machine and I am using wine currently (I cannot mess with packages too much just now). I will provide a back trace for newer wine version ASAP.
Nonetheless the back trace should be of some help since the problem is probably a regression and is antecedent to 1.4.1.
Best Regards, Gabriele Dini Ciacci
http://bugs.winehq.org/show_bug.cgi?id=31665
--- Comment #7 from Frédéric Delanoy frederic.delanoy@gmail.com 2013-06-22 08:10:10 CDT --- (In reply to comment #6)
I had already read the guide for wine on 64 bits, but sadly it did not helped much in my case (naturally considering also the limited time factor). Thanks for the link anyway.
I include the back trace with debugging symbols installed (thanks for the tip, i was stupid to not do that at first). They are for version 1.4.1 of wine, since this is a production machine and I am using wine currently (I cannot mess with packages too much just now). I will provide a back trace for newer wine version ASAP.
Nonetheless the back trace should be of some help since the problem is probably a regression and is antecedent to 1.4.1.
Best Regards, Gabriele Dini Ciacci
Seems you forgot to attach the backtrace
http://bugs.winehq.org/show_bug.cgi?id=31665
Gabriele Dini Ciacci dark.schneider@iol.it changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #41633|0 |1 is obsolete| |
--- Comment #8 from Gabriele Dini Ciacci dark.schneider@iol.it 2013-06-22 08:13:05 CDT --- Created attachment 44904 --> http://bugs.winehq.org/attachment.cgi?id=44904 Back trace with debug symbols femap 10.1 with wine 1.4.1
Back trace with debug symbols for wine version 1.4.1.
The bug is triggered with file->rebuild option. The bug happen mostly often and even on blank database file (a new blank project).
Partially obsoletes my previous back trace since this one has debug symbols, but the other one was with newer wine 1.5.12 version and newer femap 10.3 version. The bug persists in various femap versions.
The problem may become worse with femap 11 version, as this version performs the "rebuild action" always automatically, but I did not had chance to test yet. In that version just opening a file should cause a crash (as it did sometimes with older femap versions if the program guessed that the file needed a "rebuild").
http://bugs.winehq.org/show_bug.cgi?id=31665
Dan Kegel dank@kegel.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |dank@kegel.com
--- Comment #9 from Dan Kegel dank@kegel.com 2013-06-22 10:17:42 CDT --- Does 'winetricks comctl32' work around the problem?
http://bugs.winehq.org/show_bug.cgi?id=31665
Michael Stefaniuc mstefani@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords|Abandoned? |
https://bugs.winehq.org/show_bug.cgi?id=31665
--- Comment #10 from Rosanne DiMesio dimesio@earthlink.net --- Is this still an issue in current Wine (1.7.36 or later)?
https://bugs.winehq.org/show_bug.cgi?id=31665
--- Comment #11 from Gabriele Dini Ciacci dark.schneider@iol.it --- Hello,
I just tested with Femap 10.3 and wine 1.7.36.
The bug is still present and triggered in the same way.
https://bugs.winehq.org/show_bug.cgi?id=31665
--- Comment #12 from Ken Sharp imwellcushtymelike@gmail.com --- (In reply to Austin English from comment #1)
Please run a regression test: http://wiki.winehq.org/RegressionTesting
Still needed.
https://bugs.winehq.org/show_bug.cgi?id=31665
--- Comment #13 from Gabriele Dini Ciacci dark.schneider@iol.it --- You are completely right.
Currently I do not have access to Femap (and not to the new version of it that is 11.2).
Last time, when I tried to run a regression test, the thing proven not trivial for me and I had to leave it after it has eat some hours.
I am unsure of when I will find the time to provide a regression test.
https://bugs.winehq.org/show_bug.cgi?id=31665
winetest@luukku.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |winetest@luukku.com
--- Comment #14 from winetest@luukku.com --- (In reply to Gabriele Dini Ciacci from comment #11)
Hello,
I just tested with Femap 10.3 and wine 1.7.36.
The bug is still present and triggered in the same way.
Could you test wine 1.8, 1.9 or 2.0 series?
https://bugs.winehq.org/show_bug.cgi?id=31665
joaopa jeremielapuree@yahoo.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jeremielapuree@yahoo.fr
--- Comment #15 from joaopa jeremielapuree@yahoo.fr --- https://need-for-speed-most-wanted-demo.en.softonic.com/
https://bugs.winehq.org/show_bug.cgi?id=31665
--- Comment #16 from joaopa jeremielapuree@yahoo.fr --- Is still a bug in current wine(3.20)?
https://bugs.winehq.org/show_bug.cgi?id=31665
--- Comment #17 from joaopa jeremielapuree@yahoo.fr --- No download. No news from the OP since 5 years. Can an administrator close this bug as ABANDONED?
https://bugs.winehq.org/show_bug.cgi?id=31665
--- Comment #18 from Dan Kegel dank@kegel.com --- I think this is the app: https://www.plm.automation.siemens.com/store/en-us/trial/femap.html
and this is the appdb entry: https://appdb.winehq.org/objectManager.php?sClass=application&iId=5209
Demos are not public, it seems...
https://bugs.winehq.org/show_bug.cgi?id=31665
--- Comment #19 from Gabriele Dini Ciacci dark.schneider@iol.it --- Technically I am still following the bug, but yes, if it's abandoned on your side... just do not assume it is fixed.
I do not have access to the software anymore and demos require a registration.
The software is a core software because as any professional product cannot be replaced (some calculations have to be performed using the same software as prescribed by some regulations).
[polemic removed] you might guess the frustration.
https://bugs.winehq.org/show_bug.cgi?id=31665
Nikolay Sivov bunglehead@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|-unknown |comctl32
--- Comment #20 from Nikolay Sivov bunglehead@gmail.com --- (In reply to Gabriele Dini Ciacci from comment #19)
Technically I am still following the bug, but yes, if it's abandoned on your side... just do not assume it is fixed.
I do not have access to the software anymore and demos require a registration.
The software is a core software because as any professional product cannot be replaced (some calculations have to be performed using the same software as prescribed by some regulations).
[polemic removed] you might guess the frustration.
That's understandable. We had a crash fix since then that might be related, https://source.winehq.org/git/wine.git/commit/60fedd23f95c66f4dce06c5c447de9.... According to 'git describe' first release to contain it is wine-1.8 (or wine-1.7.55~253). If you have time please retest with 1.8+.
(In reply to joaopa from comment #17)
No download. No news from the OP since 5 years. Can an administrator close this bug as ABANDONED?
Let's not do this. Crash was clearly described, software is technically available, even if after registration like most of Siemens products today.
https://bugs.winehq.org/show_bug.cgi?id=31665
Samantha Humphrey sklein@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |sklein@codeweavers.com
--- Comment #21 from Samantha Humphrey sklein@codeweavers.com --- Tested with wine 7.7 and the current FEMAP Trial download (version 2021.2). System requirements called for 64-bit. File > Rebuild did not result in a crash. I also attempted to download some sample .bdf files as mentioned - there were errors reported but the application did not crash. Please let me know if there are other ways in which I can test this, but it appears to be working now (several years later.)
https://bugs.winehq.org/show_bug.cgi?id=31665
Ken Sharp imwellcushtymelike@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED
--- Comment #22 from Ken Sharp imwellcushtymelike@gmail.com --- Reported fixed. Please reopen if still an issue in Wine 9.8 or later.
https://bugs.winehq.org/show_bug.cgi?id=31665
--- Comment #23 from Gabriele Dini Ciacci dark.schneider@iol.it --- Sorry for the noise, but I morally HAVE to thank you all for your hard work.
Open Source is like True Love. It will always prevail.
It took 12 years, but we all did it.
Thank you, I love you all. Gabriele
https://bugs.winehq.org/show_bug.cgi?id=31665
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #24 from Alexandre Julliard julliard@winehq.org --- Closing bugs fixed in 9.9.