Panic over invalid memory address or nil pointer dereference on invalid subcommand

Question

Panic over invalid memory address or nil pointer dereference on invalid subcommand

Sam-Izdat opened this issue 10 years ago · 4 comments

There appears to be a slight problem right here. I haven't tried to really tree this one, but it seems, if a bad subcommand name is given by the user, subcmd references no SubCommand so calling subcmd.errf() gives go a conniption fit before it can proceed with the error handling.

jwaldrip commented 10 years ago

Fixed

Answer 1 · 2014-10-13T14:34:56.000Z

@Sam-Izdat I have a fix that will be coming out in the next release later today. Thanks for finding this.

#4

Answer 2 · 2014-10-13T20:44:00.000Z

@jwaldrip Sweet! Thanks for making this library available. It's really made my life a lot easier.

Answer 3 · 2014-10-13T21:03:01.000Z

@Sam-Izdat glad you like it!