BRL-CAD Bugs
============

Bugs should be reported to the bug tracker on the project website at
http://sourceforge.net/tracker/?atid=640802&group_id=105292

The bugs and issues listed in here may or may not be the same as or
related to the bugs reported to the bug tracker.  In general, users
should not look to this file for information regarding the status of
bugs.  Informal bug-related information that is intended for
developers will generally be found here.  This may include short term
issues that are in active development as well as long term and
on-going issues.

Recent Bugs
-----------

* "touch file.g && mged -c file.g units m" results in a BU_ASSERT
  failure and bombs.

* libfb cannot utilize standard output/error "device" files without
  path trickery.  it recognizes the /dev/ prefix and presumes it's a
  libfb device instead of a filesystem device.

   OK: rt -F/./dev/stdout
  BAD: rt -F/dev/stdout

* libfb cannot open a file descriptor when piping/redirecting output.

   OK: rt -F/./dev/stdout moss.g all.g
  BAD: rt -F/./dev/stdout moss.g all.g > test.pix

* ray-tracers assume a seekable output stream.  libfb reports numerous
  fseek errors and outputs slightly corrupted pix data.

   OK: rt -o test.pix moss.g all.g && pix-png test.pix > test.png && rm -f test.pix
  BAD: rt -o /dev/stdout moss.g all.g | pix-png > test.png

* running any of the various mged commands (e.g. clicking the raytrace
  button many times quickly, or running rtarea on a large model) that
  output a lot of data will hang mged (idle cpu utilization).

* mged in console mode goes into an inf loop if you try to read from
  stdin using Tcl routines (e.g. read stdin, fgets stdin blah).

* mged in GUI mode rejects reads on stdin

* solids.sh regression test fails on Mac OS X with one pixel
  off-by-many on the edge of the middle ARB8 when using an optimized
  -O3 compile (-fno-unsafe-math-optimizations makes no difference)

* tessellation of some pipe in toyjeep.g fails (rather reliably) on
  some given bend

* tgc reports one hit errors though hit point has 0,0,0 direction
  implying that maybe the point was supposedly deleted.

* rtedge is not respecting the -c"set" options.  needs to give some
  indication that they were parsed too since it ignores unrecognized
  values apparently.

* fbhelp sends some of the output to stdout and some to stderr...

* debugbu 2 immediately reports a bu_vls_free() error.. apparently
  been a problem since 4.5 days.  this occurs because
  bu_memdebug_add() is not called unless memory checking is enabled
  via bu_debug.  so when bu_debug is set to 2 or 3, it ends up
  reporting errors during bu_free() for items that were allocated and
  were not yet being tracked.

* mged View menu says I and O are keybindings for zoom in/out -- they
  are apparently not.

* usage of lt says "lt object", yet if you actually type exactly that,
  you get a bus error.  Nice.

* raytracers report the wrong amount of cumulative time (reports as
  0.0 seconds elapsed) on amd64 linux; most likely the same pthread
  accounting bug visited a couple years ago.

* Create menu.. create "part" boo hiss..

* xpush sometimes doesn't work, e.g. objects with empty trees,
  resulting in the db being left in a bad situation.

* wavelet isn't working correctly on a simple image decomposition &
  reconstruction.

* query_ray can't find nirt if not installed

* fbed is looking for /usr/lib/vfont/nonie.r.12

* mged doesn't check if html_dir does not exist when searching for
  docs/browser.

* permute then translate doesn't refresh the graphics window
    permute 4378
    translate menus
    p 0 0 0
    p 0 0 0

* constrained axis translation bindings on OS X don't work
    object/matrix edit
    shift-alt mouse (left/mid/right for x/y/z respectively) should work

* mged documentation doesn't open on OS X

* mged command prompt will have the cursor reset to before the 'mged>'
  prompt after certain actions like page up/down.  the cursor will
  sometimes remain offset after issuing subsequent commands.

* the findfont directive in gv postscript is reporting font not found

* concave arbs give correct wireframe but do not raytrace correctly.

* rtwizard/rtedge creates incorrect "fuzzy" edge overlay when creating
  a "Ghost Image with Insert and Lines" that includes a light source
  and object close to surface (e.g. moss.g; select plane, light, and
  cone for ghost; select cone for insert and lines.)

* rtwizard doesn't work with perspective

* mged's solid illuminate doesn't work when Lighting is turned on

* raytrace of -s64 and remote -F/dev/Xl crashes inside a memcpy during
  the first fb_write().  seems to only occur on an unbuffered render
  to a X24 framebuffer, incremental/buffered worked fine.  acts like
  stack corruption.

* g2asc exports attr lines but will not grok them on asc2g

* mged's matrix selection does not modify the correct matrix if there
  are multiply referenced non-unique paths (e.g. referencing the same
  object N times in a combination).

* facetize -t doesn't work (tnurb support)

* on os x, the -fast option results in an odd optimization/aliasing
  bug where rtip contents are lost in rt after returning from
  rt_gettrees().

* report of rtwizard hanging at 40% on Debian (from binary distro)

* make extrude crashes

* tra in console mode outputs a warning about mged_players

* mged primitive editor doesn't accept/apply values to disk for
  certain primitives (e.g. sph)

* photon map cache file doesn't work (seems to crash rt on use)

* enabling perspective mode horks shaded mode, also Z clipping
  shouldn't be required to get the shading.

* an underlay framebuffer does not underlay with shaded mode

* bu_malloc() function and company take an unsigned int argument and
  will overflow without notification (since it is unsigned) resulting
  in less memory allocated than one requested.

* rtweight chokes on a .density file that has less than 3 values per
  line (infinite loop).  also gives infinite areas when presented with
  an empty .density file.

* setting src/librt/db5_io.c's AVS_ADD off in db5_import_attributes
  causes bad things to happen and it really shouldn't.

* vrml exporter (and probably others) doesn't export primitives
  directly as one might expect like the ray-tracers, only regions.

* if you turn off compilation of tcl/itcl, btclsh/mged fail to find
  their scripts.

* sketches extruded with non-square AB vectors results in inner sketch
  components not getting scaled properly.

* rtcheck is ignoring fastgen tagged geometry since no multioverlap
  handler is set.

* bot-bldxf fails in db_walk_tree(), interface may have changed

* bwmod gives a divide by zero error whenever you use the "-d" option

* you can't run a make benchmark unless you're compiling in place


Older Bugs
----------

* several manpages are missing or out of date for various tools

* X11 framebuffer often fails to display on certain middle bit depth
  displays. (e.g. 15 or 16 bit depth)


Annoyances
----------

* matrix edits on objects in mged require you to select a primitive
  for a coordinate system reference.  this can be counterintuitive and
  confusing.

* there are frequently modality errors when entering edit mode as
  control and middle mouse rebind to model edit instead of view edit.

---
Bugs should be reported to the bug tracker on the project website at
http://sourceforge.net/tracker/?atid=640802&group_id=105292

BUGS should be formatted to column 70 (M-q in emacs), no tabs.
