On 12/27/2012 10:32:51 PM, Ashwini Sharma wrote:
Hi Rob,
With your fix, it doesn't segfault now.
But does it matter, to give the proper option name in error message.
If
yes, then the
fix fails in that.
e.g. when running *./toybox touch -d 12 -r f2 f1* it throws the error
message as
*touch:
Hi Rob,
With your fix, it doesn't segfault now.
But does it matter, to give the proper option name in error message. If
yes, then the
fix fails in that.
e.g. when running *./toybox touch -d 12 -r f2 f1* it throws the error
message as
*touch: No 'r' with 't'*.
I feel the error message is not exp
On 12/27/2012 11:06:37 AM, Felix Janda wrote:
When trying to implement the remaining options for "pwd" I could also
test
toybox's group option handling.
The option string I wanted to use is: ">0LP[!LP]"
(It's the same for "LP[!LP]".)
With the current argparsing I get a segfault for "pwd -L -P
When trying to implement the remaining options for "pwd" I could also test
toybox's group option handling.
The option string I wanted to use is: ">0LP[!LP]"
(It's the same for "LP[!LP]".)
With the current argparsing I get a segfault for "pwd -L -P". When enabling
TOYBOX_DEBUG it says "pwd: traili
On 12/26/2012 10:24:53 PM, Ashwini Sharma wrote:
Hey Rob,
Options mutual exclusion handling is having a Seg Fault in function
gotflag.
I think that means you referenced an option that doesn't exist. (If you
enable TOYBOX_DEBUG in the config, it's supposed to catch this and spit
out an "un
