Dubugging GCK2.5 under wine

Last modified on July 24, 2026 • 1 min read • 169 words
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.
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.