[plt-scheme] segfault in 299.102 x86 linux
To repro, save the attached file as "call.ss", then at the shell, type
mzscheme --require call.ss
If you're like me, you'll then get a segfault with this stack trace:
#0 0x080b07e2 in check_cycles_fast (obj=0x0, pp=0xbffff380) at print.c:514
#1 0x080b091b in check_cycles_fast (obj=0x88cff00, pp=0xbffff380) at print.c:551
#2 0x080b1020 in print_to_string (obj=0x88cff00, len=0xbffff4a0, write=0, port=0x0, maxl=-1, check_honu=0) at print.c:743
#3 0x080b10de in print_to_port (name=0x0, obj=0x0, port=0x8284f50, notdisplay=0, maxl=0, check_honu=0) at print.c:782
#4 0x080b03e5 in scheme_internal_display (obj=0x0, port=0x0) at print.c:370
#5 0x080ae66c in display_write (name=0x81178b4 "display", argc=135648972, argv=0x8285f98, escape=1) at portfun.c:3678
#6 0x080ae7c9 in display (argc=0, argv=0x0) at portfun.c:3727
#7 0x0806dfc0 in scheme_do_eval (obj=0x82bb760, num_rands=1, rands=0x8285f98, get_value=-1) at eval.c:3376
#8 0x0806e1cb in eval_k () at eval.c:4349
#9 0x08076942 in top_level_do (k=0x806e070 <eval_k>, eb=1, sj_start=0x0) at fun.c:1086
#10 0x08076c82 in scheme_top_level_do (k=0, eb=0) at fun.c:1131
#11 0x0806e2b0 in scheme_eval_compiled_multi (obj=0x0, env=0x0) at eval.c:4384
#12 0x0806f60b in scheme_eval_string_all (str=0x0, env=0x8288ea0, cont=0) at eval.c:4952
#13 0x0805bcbb in finish_cmd_line_run (fa=0x8362ee0, repl=0x805cad0 <do_scheme_rep>) at cmdline.inc:252
#14 0x0805caca in cont_run (f=0x0) at main.c:364
#15 0x0805c8e1 in run_from_cmd_line (argc=0, _argv=0xbffffb04, mk_basic_env=0x805cb20 <scheme_basic_env>, cont_run=0x805cab0 <cont_run>) at cmdline.inc:951
#16 0x0805ca92 in actual_main (argc=0, argv=0x0) at main.c:353
#17 0x0807cc89 in scheme_image_main (argc=0, argv=0x0) at image.c:765
#18 0x0805ca4c in main (argc=0, argv=0x0) at main.c:263
-------------- next part --------------
A non-text attachment was scrubbed...
Name: call.ss
Type: application/octet-stream
Size: 1440 bytes
Desc: guilty module
URL: <http://lists.racket-lang.org/users/archive/attachments/20050419/953bdad3/attachment.obj>
-------------- next part --------------
--
If you can't change your underwear, can you be sure you have any?