Hi all, While debugging an error in my program, DrScheme 4.2 crashed with a segmentation fault. So I got the latest svn 15438 and compiled with -ggdb. Started DrScheme and it still segfaults.
With mzscheme also segfaults: $ ~/Applications/plt/plt-r15438d/bin/mzscheme -t main.scm EBoC - Event-B Model Checker ---- Version: 0.1 ---- ---- by: Paulo J. Matos ---- Running in mode esmc. Timing for: Parsing (cpu 140, real 152, gc 0) Timing for: Interpret Identifiers (cpu 270, real 306, gc 30) SIGSEGV fault on 0x4c8 Aborted So, I went in gdb: $ gdb ~/Applications/plt/plt-r15438d/bin/mzscheme GNU gdb 6.8 Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-pc-linux-gnu"... (gdb) set args -t main.scm (gdb) run Starting program: /home/pmatos/Applications/plt/plt-r15438d/bin/mzscheme -t main.scm Program received signal SIGSEGV, Segmentation fault. 0x0000000000669c3d in scheme_gmp_tls_unload (s=0x7f6823ef92b0, data=0x0) at /home/pmatos/Applications/plt/plt-svn/src/mzscheme/src/gmp/gmp.c:5810 5810 s[0] = 0; This is worse, because I really don't think this is the same problem given nothing was really printed. I think the problem showing in gdb is different meaning I cannot really reproduce my initial segfault under gdb. Any tips? Cheers, -- Paulo Jorge Matos - pocmatos at gmail.com http://www.pmatos.net _________________________________________________ For list-related administrative tasks: http://list.cs.brown.edu/mailman/listinfo/plt-dev
