Closed GoogleCodeExporter closed 9 years ago
It might have been essential to know which WID caused the problem, and also to
have some debug output (use -v option, or press "v" in TUI).
I suppose you didn't want to actually check out the archived cache GCXXXX in
New Jersey, did you?
Original comment by Steve8x8
on 23 Jul 2012 at 9:00
I just reproduced the error with GC3QJ2H. No I didn't mean the actual GCXXXX ;)
Original comment by julianke...@googlemail.com
on 24 Jul 2012 at 5:48
I just noticed the crash I thought to have reproduced was because of having
used the wrong path in --output. If you find the bug anyway It's good, else
close the issue, waypoint search works for me it seems.
Original comment by julianke...@googlemail.com
on 24 Jul 2012 at 6:05
Can you try to reproduce the bug, and send verbose output?
I seem to be unable to find the culprit - a bad target directory should be
effective in output.rb, not search.rb, so this sounds like a red herring to
me...
Original comment by Steve8x8
on 4 Sep 2012 at 8:23
No additional info for months, therefore no way to reproduce this bug. Closing
as WontFix.
Original comment by Steve8x8
on 30 Dec 2012 at 3:02
Original issue reported on code.google.com by
julianke...@googlemail.com
on 15 Jul 2012 at 4:08