http://bugs.winehq.org/show_bug.cgi?id=18022
--- Comment #4 from Mikko Rönkkö mikko.ronkko@iki.fi 2009-04-13 06:57:09 --- I meant to post a longer description instead of just the log file, but for some reason failed to do so. Sorry for the confusion.
(In reply to comment #3)
Hello,
--- quote --- $ wine p2.exe /Volumes/KINGSTON/P2kivaNEW/ --- quote ---
Unfortunately your backtrace doesn't contain anything useful info, debug symbols are missing - but this won't helper either. You need to supply the sample data as attachment (compressed) so one can reproduce the same behaviour.
I cannot provide this particular data, since it is real data and has confidentiality issues. Additionally, it is huge.
I will create a sample data and post it here when I have first tested that it works with Windows first.
The way I run this software in Windows is that I type in the name of the program (p2) followed by a path to the input files. I would run this same analysis by typing
p2.exe Z:\P2kivaNEW\
So the path here differs, but this should not be an issue, right?
E.g. the content of "P2kivaNEW" directory which is given as parameter to app or at least a simplyfied/stripped down version of project files which work in Windows.
I am working on this.
--- quote --- This is with mac and Wine 1.1.17 --- quote ---
Again: did you run the app with the same command line and data in Windows? If it crashes, this bug is INVALID.
The application does work with windows.
I will create sample data and do a sample run on Windows and then post the results of that, the same run on Wine, and the data files used.
Thanks for your help,
Mikko