Bug Database for Sun ONE Studio 8

Question

Is there an online bug database for the Sun ONE Studio 8 Compiler Collection, like there is for all of the Java related tools? I know we have product support, but I don't want to go through the overhead of 4 or 5 layers of people to report a minor problem I have found.
The minor problem is that the er_src utility will open files in the current working directory in preference to an absolute pathname specified on the command line. I used it from my home directory, giving it an executable name and source file name each about 5 levels deep in directories below my home -- with absolute paths. I was shocked to see the source from a six year old version of the file in the output. The 'truss' utility revealed that the source was being opened from my current directory -- ignoring the absolute path. This version of the file is one I have kept for reference, being the initial port of the program from a different language.
It appears that er_src attempts the unqualified file name first, then the absolute path if it fails to find the unqualified name.

Answer 1

The er_src man page does say the .er.rc files are processed, which implies that the setpath/addpath handling is done, at least to me. So the behavior reported is what I would have expected, but the manpage could, and should be more explicit.
The er_print man page is more specific, and does say that the compiled-in path is used only if the file is not found searching the current path mappings, which do contain "."
Can you tell me exactly what you'd like us to do? We did it this way because users complained about using the compiled in path, rather than finding the file in . or the experiments, where we explicitly tell people to copy files for archival purposes.
If you want us to change the behavior, please tell us EXACTLY what the desired behavior is. We could define a special symbol, like $EXPTS, to refer to the compiled-in path, $COMPPATH, perhaps, and then it could be put before or after . or $EXPTS.
Another issue is which name to use when. er_src has two referents for a path, one for "object", the thing whose source is being dumped, and a second for "item", specifying which item contained in the object should be dumped. For item, I believe we always only use the
base name, even if an absolute name is given. It is used to match against the names contained in object's symbol tables. All of this is complicated by NFS -- the present functionality is intended to behave gracefully when a file is examined on a machine other than the one on which
it was compiled.