xmlgraphics-batik-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 46103] Review various possible bugs detected by Jtest
Date Tue, 28 Oct 2008 21:27:11 GMT
https://issues.apache.org/bugzilla/show_bug.cgi?id=46103


Mirko Raner <mirko@raner.ws> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #22781|0                           |1
        is obsolete|                            |




--- Comment #4 from Mirko Raner <mirko@raner.ws>  2008-10-28 14:27:10 PST ---
Created an attachment (id=22785)
 --> (https://issues.apache.org/bugzilla/attachment.cgi?id=22785)
Jtest Static Analysis for Apache Batik (trunk)

As requested by Helder, I re-ran a slightly modified configuration on the SVN
trunk over lunch and attached the report. I took out the TRS.SOUF rule about
possible synchronization problems, as Dieter mentioned that he was well aware
of the issue. In turn, I enabled a rule for detecting the broken Double Checked
Locking pattern, which promptly found a violation. Also, I added detection of
unused package-private fields and methods. Unless there is some fancy
Reflection API access going on somewhere those fields and methods can probably
be removed.

The attached results were all produced by simple static analysis, i.e. pattern
matching assisted by some additional collected information about type
hierarchies, mutability, etc. Jtest can also perform a full flow analysis,
which is essentially a partial simulation of executed code and finds bugs that
are caused by scenarios that may involve multiple classes. In the reports I
attached, this type of analysis was not enabled, mainly for two reasons: (1) it
can obviously take a very long time to run, which would exceed the scope of our
internal testing of open source projects, and (2) the bugs indeed turn out to
be more "sophisticated", involving multiple correlated stack traces which are
typically very hard to explore without the corresponding UI in Jtest. Anyway,
if I get a chance and can find a machine with some spare CPU cycles I can try
running flow analysis and send you the report. But don't hold your breath for
that right now.


-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: batik-dev-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: batik-dev-help@xmlgraphics.apache.org


Mime
View raw message