Debugging GCK2.5 under wine

Fri, 25 May 2007 00:00:00 +0000

GCK2.5.9 works with wine (crossover office 2.01 version). The 2.5.9 update doesn’t show the “Could not start the application because there is not enough memory” error. GCK starts up without any trouble and is partially usable. In fact it seems to be fully functional (including Deluxe import) with one big exception: new files cannot be created (quits upon selecting “File - New”. The empty window box where you can select what type of GCK file you want to create (sequence, illustration, etc) is drawn with the title “New Window”, but its not filled with content and the application quits.

Dubugging GCK2.5 under wine

Fri, 25 May 2007 00:00:00 +0000

The new window that fails to be displayed, contains (when run natievly under W2K) the following text (and radio buttons for the four different file types):Select File Type Contruct (Ctrl-C)Illustration (Ctrl-I)List (Ctrl-L)Gel (Ctrl-G)New File NameOKCancelThe text associated with the different radio buttons appears first in the debug file in the following lines (as determined by the command “grep -n “List” all_output > List_output”, etc): 3890577 Gel3885836 Illustration3881107 List3876329 ConstructThat is within the range where we predicted the error to be. Let’s now look at what happend shortly before and after these commands were issued. After using GCK2.5 under wine a little bit more, I noticed that there is another function that causes the program to crash without error message, namely the “find sequence” function. Also in this case a dialog is displayed in which the user is supposed to type in a nucleotide sequence. Maybe there is something in common for these two crashes which could help to identify the crucial system call that makes the program to crash.

Debugging on Michael’s Domain

Debugging GCK2.5 under wine

Dubugging GCK2.5 under wine