Proguard 4.4beta3 gets stuck (cpu is running at 100%) when obfuscating a jar file. The obfuscation is run to get a map file only (for later processing), and is run with the options listed below. The input file (a.jar) has been processed by proguard 4.4beta3 in a step before this one (options are the same, but the keep specs are different).
I'm running Windows Vista, jdk1.6.0_04, ant 1.7.0...
2009-07-07 08:53:23 UTC in ProGuard Java Optimizer and Obfuscator
