Age | Commit message (Collapse) | Author |
|
|
|
Bug: 26555886
Change-Id: I9045628003e69b50bb50d71253729e7e525f57e3
|
|
am: a90d411690
* commit 'a90d411690b2a62d42e7937a1e98d31de5e3c1f6':
Rebuild proguard.jar with ant/gradle support.
|
|
am: b29a267e02 -s ours
* commit 'b29a267e02f80873fa1697989112e2500c432e44':
Fix 'Exception in thread "main" java.lang.AbstractMethodError:'
|
|
|
|
|
|
By setting ANT_HOME and GRADLE_HOME in build/build.sh.
Bug: 26274804
Change-Id: Iad81e3f81759ebb3461bfedfc2fed0b0229acca8
(cherry-pick from commit eedc65a59bf96c2075b7feecae6c5fd1d3713e9e)
|
|
When running with OpenJDK 8 (openjdk version "1.8.0_45-internal") on
module messaging, sometimes an odd exception is caught in main:
Exception in thread "main" java.lang.AbstractMethodError:
java.lang.Exception.getMessage()Ljava/lang/String;
at proguard.ProGuard.main(ProGuard.java:519)
It's not 100% reproducible. But it's certain to happen if you run the
same ProGuard tasks in parallel (e.g. x40).
The exception runtime type is actually
java.lang.ArrayIndexOutOfBoundsException, which I tracked down to
raise from MappingPrinter.visitLineNumberTableAttribute().
It's strange that the exception object is in a weird state that
e.printStatckTrace() throws java.lang.AbstractMethodError.
Other people have seen similar things too:
http://stackoverflow.com/questions/6777710/abstractmethoderror-on-calling-exception-printstacktrace
Using temparary variables low/high fixes the crash.
It seems to be an OpenJDK 8 bug.
Rebuilt the jar files by running build/build.sh.
Bug: 26274804
Change-Id: I773023b2dc57bd048c6781aded84e0c0df923a90
(cherry-pick from commit 9d99b19da7ab70bfff55327c5e4719addb1955f7)
|
|
By setting ANT_HOME and GRADLE_HOME in build/build.sh.
Bug: 26274804
Change-Id: Iad81e3f81759ebb3461bfedfc2fed0b0229acca8
|
|
When running with OpenJDK 8 (openjdk version "1.8.0_45-internal") on
module messaging, sometimes an odd exception is caught in main:
Exception in thread "main" java.lang.AbstractMethodError:
java.lang.Exception.getMessage()Ljava/lang/String;
at proguard.ProGuard.main(ProGuard.java:519)
It's not 100% reproducible. But it's certain to happen if you run the
same ProGuard tasks in parallel (e.g. x40).
The exception runtime type is actually
java.lang.ArrayIndexOutOfBoundsException, which I tracked down to
raise from MappingPrinter.visitLineNumberTableAttribute().
It's strange that the exception object is in a weird state that
e.printStatckTrace() throws java.lang.AbstractMethodError.
Other people have seen similar things too:
http://stackoverflow.com/questions/6777710/abstractmethoderror-on-calling-exception-printstacktrace
Using temparary variables low/high fixes the crash.
It seems to be an OpenJDK 8 bug.
Rebuilt the jar files by running build/build.sh.
Bug: 26274804
Change-Id: I773023b2dc57bd048c6781aded84e0c0df923a90
|
|
This will be used for automated notification of external vulnerability
reports.
Change-Id: I9aabbe75a1a06d0ec3421ac5e78c786a22e27325
|
|
* commit 'baa6a15c85c8ab803b580f3fcbd1eecfbbe9c3a7':
Add MODULE_LICENSE file
|
|
|
|
Change-Id: Ia519f00065573092f0ef3e8ab8ce88258bd1ae86
|
|
* commit '6af8f1004e0efe02a138286a34e833d1f3d227d7':
Upgrade Proguard to 5.1.
|
|
|
|
Downloaded from:
http://sourceforge.net/projects/proguard/files/proguard/5.1/
Bug: 17550647
(cherry picked from commit 2270795fbe0b277bfd49f40950ecaa78583175cc)
Change-Id: I4d4c6b4f11aca8d5595b7f285c675bc5873d5e24
|
|
Downloaded from:
http://sourceforge.net/projects/proguard/files/proguard/5.1/
Bug: 17550647
Change-Id: I2b4eab16eb7821fc232b294ab7f433aae08f71e1
|
|
* commit '3fd19dba2bdc0c4b64afda4d75836e1dcf7abf97':
Increase the java heap to 512M when running proguard
|
|
All of us building on Macs are running out of java heapspace during the
proguard phase of the build. This CL fixes the problem.
Change-Id: I461bb14b2ff2491e43ef8e2312e76a2a8fc0ee24
|
|
Change-Id: I727039a1eb945a438432d5bab078379a27854c8f
|
|
|
|
Downloaded from:
http://sourceforge.net/projects/proguard/files/proguard/4.10/
Bug: 8992787
(cherry picked from commit b9cc48a43ed984587c939d02fba5316bf5c0df6e)
Change-Id: I6c619bc8b0493530470e134127a04c7143aeee2d
|
|
of memory on some apps.
(Resurrecting 3082b4a5fc45bc123067c9a984f90b7706704c59 which was lost in b9cc48a43ed984587c939d02fba5316bf5c0df6e)
Change-Id: I0868e7fbb944aa48a4ef29880fb0cc5faa51c2e7
|
|
Downloaded from:
http://sourceforge.net/projects/proguard/files/proguard/4.10/
Bug: 8992787
Change-Id: Ia07cc5b3feed443982b7e8f2a1f361479e735b18
|
|
So it supports Android Bugreport Syntax
Change-Id: I09713b53364a2e4cda44ee67325f183a54075433
|
|
build runs out of memory
building the Utopia jar file.
Change-Id: Id3491f1f8f1640aa532c5ec30353d26a8d7ff8ac
|
|
This reverts commit cfead78069f3dc32998dc118ee08cab3867acea2.
Bug: 6079915
|
|
Change-Id: Ie185d0be411a80cc6a330cafa8547252a7dc1d9c
You can find the changelog here
http://proguard.sourceforge.net/#downloads.html
|
|
* commit 'd889ce6df1a831f4cff915b4c2a48090ece14b03':
Fix proguard wrappers.
|
|
|
|
Shell version: This fixes the simple case of
the proguard binary path having a space in it.
Bat version: Use %* to capture all arguments, not
just the first 9 ones. It's typical to have > 10.
Change-Id: I32e7bcbe0c78f7518a1d727e4d80c07ec6d673b5
|
|
Change-Id: I7ebb33bf0dcbde7186dc96020f5871dc14fad5d7
|
|
Change-Id: I5e7a3a7161faf357d09d34b3dba61c52be7ace07
|
|
Merge commit '198fe95bdbe59b9d2048c9ccb015132bfed578b2' into eclair-plus-aosp
* commit '198fe95bdbe59b9d2048c9ccb015132bfed578b2':
android-2.1_r1 snapshot
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|