'kill %%' and 'kill %+' segfault

[McDutchie]

Any reference to the current job (%% or %+) before there is one, passed to the kill command, currently causes a segfault. This is also the case in the 93u+ 2012-08-01 release. For example:

$ ksh -c 'kill -s STOP %%; echo exit status $?'
Segmentation fault: 11

Backtrace from lldb:

* thread #1, stop reason = signal SIGSTOP
  * frame #0: 0x000000010ff80944 ksh`job_kill + 20
    frame #1: 0x000000010ff80809 ksh`job_walk + 309
    frame #2: 0x000000010ff5856d ksh`b_kill + 806
    frame #3: 0x000000010ffab18b ksh`sh_exec + 16128
    frame #4: 0x000000010ff5f48b ksh`exfile + 3243
    frame #5: 0x000000010ff60387 ksh`sh_main + 3367
    frame #6: 0x00007fff5832b3d5 libdyld.dylib`start + 1

---

edit: Same happens when using %- to refer to the previous job before there is one.