I'm seeing some similarities between a failure in g-nff and other, similar tesselating converters. On the same .g file, some bomb and throw "(BRL-CAD)-nnnnn-bomb.log", and some don't. but they all seem to fail on the same region.
Is there any way to turn off or change the behavior of bu_bomb/bu_log for the converter programs so I can capture info from stderr and stdout without bothering the executables internally? I know I can use 'script' if I have to but would rather not. I would like to try them all so I can easily determine to which set they belong (and document that in TODO) for further investigation of the problem. And does anyone mind if I change the "(BRL-CAD)-nnnnn-bomb.log" to "BRL-CAD-nnnnn-bomb.log" (because the parens aren't pleasant for a *nix file system)? Cheers! -Tom ------------------------------------------------------------------------------ For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 _______________________________________________ BRL-CAD Developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/brlcad-devel
