We've stumbled across a scenario where the location information comes out with the method set to java and the classname ending with <init>. The problem occurs only after the first few calls to the constructors in question and we've only seen it on Aix under IBM's jre 1.4.0 - the suspicion is that their JIT is kicking in and messing the information up. Obviously, with this problem in place the likes of Chainsaw get very confused when trying to process the 'xml'.
Created attachment 15648 [details] The patch attempts to fix the problem by simply applying the same escaping mechanism to the classname as to the method name The patch attempts to fix the problem by simply applying the same escaping mechanism to the classname as to the method name
1.2.12 candidate
Applied fix in both v1_2-branch and CVS HEAD. Was not able to formulate a test to check the fix. The XMLLayout has other potential problems, but that is beyond the scope of what we should do in the log4j 1.2 branch.