Hi Juergen,
I got an error report from a debian user of the scli package stating that it segfaults on the command 'set' without arguments.
Turns out to be something simple:
scli > set
Program received signal SIGSEGV, Segmentation fault. 0x080631c6 in set_scli_regex (interp=0x8100c98, argc=0, argv=0x0) at cmds.c:926 926 if (regcomp(regex_flags, argv[1], interp->regex_flags) !=0) { (gdb) bt #0 0x080631c6 in set_scli_regex (interp=0x8100c98, argc=0, argv=0x0) at cmds.c:926 #1 0x0805e297 in scli_eval_cmd (interp=0x8100c98, cmd=0x80de890, argc=0, argv=0x0) at basic.c:867 #2 0x0805def4 in eval_all_cmd_node (interp=0x8100c98, node=0x8100ef4, s=0x81015ec) at basic.c:790 #3 0x0805e05a in eval_all_cmd_node (interp=0x8100c98, node=0x8100ee0, s=0x81015ec) at basic.c:816 #4 0x0805e4c1 in scli_eval_argc_argv (interp=0x8100c98, argc=1, argv=0x810ec90) at basic.c:924 #5 0x0805e756 in scli_eval_string (interp=0x8100c98, cmd=0x81051d8 "set") at basic.c:983 #6 0x0805b7ce in mainloop (interp=0x8100c98) at scli.c:115 #7 0x0805c24a in main (argc=1, argv=0xbffffcd4) at scli.c:503
argv[1] with argv=0.. I guess there should be a test for argc==2 just before that line.
regards, Remco.