mhoes

I just noticed this bug was closed, so I downloaded the latest version of IV-Play, and can still reproduce this issue with that version.

> > ``` > [fish@centos-64 ~]$ gdb -c core.56320 > ``` I may be mistaken, but it appears from the above snippet that you are only telling gdb where the...

Minor nitpick: you stated > > ``` > ulimit -c unlimited (enable core dumps) > ``` > which strictly speaking isn't completely correct: although this does enable core dumps, more...

Second nitpick(s) : > > ## Where are "core" files written? > Traditionally, _(and regardless of the user producing the coredump)_ a core dump is written to the **current working...

Just my 2$, but I personally feel that it would be impossible to do this reliably. You would be forced to build a list of (almost) all Unix/Linux commands, in...

> > > Why does it need to be "reliable"? Well, if it isn't correct (almost) all of the time, then the sheer amount of false positives/negatives will annoy people...

Well, perhaps I am overestimating the difficulty of programmatically detecting the misspelling of the name of a function in a shellscript. Since you have stated that you program for a...

> > > just run `command -v` on every command invocation The problem with that approach (or running 'which cmd' for example), is that the results will only be accurate...