/proc/PID/stat can't be parsed when `comm` field contains spaces

$ cat a\ script.sh 
#!/bin/bash
cut -d' ' -f1-4 /proc/$$/stat
python3 -m jc /proc/$$/stat

$ ./a\ script.sh 
1377890 (a script.sh) S
jc:  Error - oc parser could not parse the input data.
             If this is the correct parser, try setting the locale to C (LC_ALL=C).
             For details use the -d or -dd option. Use "jc -h --oc" for help.

It appears that only the comm field can contain ), so a correct parser would read the entire file and consider everything between the first ( and the last ) (including spaces and newlines) to be the command.

[hvenev]

No, I’m wrong. Sorry about that. I didn’t notice the ^, and by default it matches the start of the string rather than the start of a line. So,

LGTM

[kellyjonbrazil]

Ok, looks like I have this fixed in the dev branch. Basically just swapped to regex vs. simple split(). Had to update the signature match regex to allow for newlines as well. Tests are passing.

https://github.com/kellyjonbrazil/jc/blob/dev/jc/parsers/proc_pid_stat.py

You can test this new parser by copying it to your jc plugin directory (https://github.com/kellyjonbrazil/jc/tree/dev#custom-parsers)

Magic syntax won’t work this way, but you can cat /proc/pid/$$/stat | jc --proc-pid-stat to test. This is because I also updated the signature in the top-level Proc parser.

For full testing of magic syntax and the normal --proc top-level parser you can clone the dev branch and test.

I’ll wait for some more fixes before pushing a new release with the fix.

Thanks again for your help!