[bugs #8921] LogManager.findAncestor throws exception if a logger has been garbage collected

[Steven Augart]

This mail is an automated notification from the bugs tracker
 of the project: classpath.

/**************************************************************************/
[bugs #8921] Latest Modifications:

Changes by: 
                Steven Augart <address@hidden>
'Date: 
                Fri 05/14/04 at 14:39 (EST5EDT)

            What     | Removed                   | Added
---------------------------------------------------------------------------
         Assigned to | None                      | saugart


------------------ Additional Follow-up Comments ----------------------------
Submitter:  

Would you be able to provide a test case that demonstrates this bug so that we 
can make sure that it is fixed properly?








/**************************************************************************/
[bugs #8921] Full Item Snapshot:

URL: <http://savannah.gnu.org/bugs/?func=detailitem&item_id=8921>
Project: classpath
Submitted by: 0
On: Wed 05/12/04 at 17:45

Severity:  5 - Average
Resolution:  None
Assigned to:  saugart
Status:  Open
Platform Version:  None


Summary:  LogManager.findAncestor throws exception if a logger has been garbage 
collected

Original Submission:  Because the LogManager maintains a copy of all loggers as 
weak references, loggers can be garbage collected.

This means that if a logger is GC'd, the next time the logger is looked up (via 
Logger.getLogger), an ArrayIndexOutOfBounds exception will be thrown in the 
charAt(candNameLength) statement, because candName and child will reference the 
same logger [at some point], thus candNameLength == childName.length(), 
therefore, childName.charAt(candNameLength) is out of bounds.

Follow-up Comments
------------------


-------------------------------------------------------
Date: Fri 05/14/04 at 14:39         By: saugart
Submitter:  

Would you be able to provide a test case that demonstrates this bug so that we 
can make sure that it is fixed properly?














For detailed info, follow this link:
<http://savannah.gnu.org/bugs/?func=detailitem&item_id=8921>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/