#15 "shell" command causes segfault

[Kolja Waschk]

jtag> shell bash

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 47175069667232 (LWP 25928)]
0x00002ae7ccaf1b50 in strlen () from /lib/libc.so.6
(gdb) backtrace
#0 0x00002ae7ccaf1b50 in strlen () from /lib/libc.so.6
#1 0x000000000040ff73 in cmd_shell_run (params=0x667480) at shell.c:51
#2 0x000000000040a9a6 in cmd_run (params=0x667480) at cmd/cmd.c:42
#3 0x0000000000402b28 in jtag_parse_line (line=<value optimized out>)
at jtag.c:177
#4 0x0000000000402d8d in main (argc=1, argv=<value optimized out>)
at jtag.c:203
(gdb)

[Kolja Waschk]

Logged In: YES
user_id=478715
Originator: YES

Fixed in 785. The "shell" command actually worked only if the command was given at least one more argument. Now it takes an arbitrary number of arguments. However, the current implementation is far from perfect because the command line was split by the parser into params[] (all whitespace between words stripped ) and has to be reconcatenated with single spaces to be handed over to /bin/sh... Quoting parameters should be possible with the cmd parser.

[Kolja Waschk]

Logged In: YES
user_id=478715
Originator: YES

Therefore, this bug can be closed.