i was going through the new features list in NEWS to see what cool things are in here and i saw the new checkjobs option. is it just me or does this cause a non-login bash to crash at exit which leads to an infinite loop / cpu churning ?
$ gdb bash (gdb) r vap...@vapier 0:0 bash-4.0 $ shopt -s checkjobs vap...@vapier 0:0 bash-4.0 $ exit Program received signal SIGSEGV, Segmentation fault. 0x000000000047159b in exit_or_logout (list=0x0) at ./exit.def:116 116 else if (check_jobs_at_exit && stopmsg == 0 && RUNNING (i)) (gdb) bt #0 0x000000000047159b in exit_or_logout (list=0x0) at ./exit.def:116 #1 0x000000000042b8ea in yyparse () at /Users/chet/src/bash/src/parse.y:5299 #2 0x0000000000421342 in parse_command () at eval.c:228 #3 0x0000000000421436 in read_command () at eval.c:272 #4 0x0000000000421684 in reader_loop () at eval.c:137 #5 0x0000000000421196 in main (argc=0x1, argv=0x7fffa0fe7ac8, env=0x7fffa0fe7ad8) at shell.c:741 if i do run a job first like 'sleep 60 &', then it doesnt crash, but it does just exit right away ... or if i do `gdb --args bash -l`, then it works as expected. -mike
signature.asc
Description: This is a digitally signed message part.
