GNOME Bugzilla – Bug 571346
[Win32] Need to set stack size
Last modified: 2010-04-09 02:30:40 UTC
It appears that Win32 can blow the stack too. We need to verify that the code in gnm_pre_parse_init is actually being compiled-in on windows.
For the record, test sheet by the name of "filter_IIR_master.xls" in hand. Explicit-parentheses nodes took up stack space during eval. Now fixed. That saves 10-20% in this case. Useful, but not enough.
I set a breakpoint on gnm_pre_parse_init on Windows XP. Execution stopped at line 200, which is after the HAVE_SYS_RESOURCE_H block: (gdb) b gnm_pre_parse_init [...] Breakpoint 1, gnm_pre_parse_init (argc=1, argv=0x3e5040) at libgnumeric.c:200 in libgnumeric.c (gdb) 200 libgnumeric.c: No such file or directory.
The sheet in question has a 22k cell cyclic loop. This is very close to "Doctor, when I bang my head on the wall, it hurts!"
The crash described in comment 1 (with filter_IIR_master.xls) goes away after running 'editbin.exe /STACK:30000000 gnumeric.exe'.
sum1: could you try a binary diff between patched and unpatched binary, please?
Created attachment 148980 [details] binary diff pic The edited file is on the bottom.
This problem has been fixed in our software repository. The fix will go into the next software release. Thank you for your bug report.