Unknown verification type [*] in stack map frame

最新推荐文章于 2020-02-10 11:00:13 发布
原创 最新推荐文章于 2020-02-10 11:00:13 发布 · 1.7k 阅读 · 0 ·
CC 4.0 BY-SA版权
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。

本文介绍如何下载并修改Proguard源码以实现特定的混淆需求，包括修改源码、编译过程及替换jar文件的方法。

1. 下载Ant和Proguard源码

  Ant官网: http://ant.apache.org

  Proguard官网: https://www.guardsquare.com/en/proguard


2. 修改Proguard源码: src/proguard/classfile/ClassConstants.java 
  将ATTR_StackMapTable的值StackMapTable替换为dummy，如下:



3. 编译Proguard源码
  在完成Ant环境的配置后，进入Proguard源码的buildscripts目录下，双击执行build.sh脚本(Windows系统需安装、配置Git)：



4.替换proguard.jar

(a)方法一:修改Proguard源码后,编译替换AS／ADT目录下的proguard.jar



(b)方法二:修改Proguard源码后,将编译生成的proguard.jar,放置到AS工程目录下,再配置Gradle

参考：https://www.guardsquare.com/en/proguard/manual/gradle

Chrome的启动参数
Criss@陈磊
02-23 5912
List of Chromium Command Line Switches Condition Explanation --[1]⊗ Classic, non-material, mode for the |kTopChromeMD| switch.↪ --0⊗ Value of the --profiler-timing flag that will disable timin...
Go ：测试堆采样逻辑(附完整源码)
希望我的博客，能帮上你解决学习中工作中所遇到的问题
11-01 277
Go ：测试堆采样逻辑(附完整源码)
metasploit的模块构成及功能分析
热门推荐
xysoul的专栏
04-07 1万+
metasploit的模块构成及功能分析 今天我们介绍一下metasploit的基础架构和 市面上介绍metasploit的书不少，网上metasploit的使用说明的文章更是满天飞，可是没有哪一本书或者哪一篇文章来介绍metasploit的目录结构和他的功能，今天我们就来介绍一下metasploit的文件结构和每个部分的功能以及参数。 exploit@ubuntu:/pentest/f
解决eclipse 导出jar混淆后在android studio 出apk时报unknown verification type[***]
12-28
本资源使用的方法很简单，找到sdk\tools\proguard\lib文件夹，里面有三个文件，分别是，proguard.jar，proguardgui.jar，retrace.jar，把这三个文件移出lib目录，把本资源解压出来后的三个jar文件放在lib目录下，启动proguardguie.bat，进行混淆，这样就可以解决混淆后的jar报unknown verification type[***]的问题。
AndroidStudio出现 Unknown verification type [95] in stack map frame 问题的解决办法
我是黄大仙
11-24 1076
产生问题的原因：引用的第三方库已经混淆过，再在本地进行编译混淆的时候就会报出这个错误。 解决的办法：若无法修改第三方库，则修改混淆器，重新进行编译，将新的混淆器覆盖原来的混淆器，则可以解决。 1.查看AndroidStudio所使用的proguard的版本，    路径为D:\Program Files\Android\Android Studio\gradle\m2repository\n
Proguard 混淆是出现 Unknown verification type [*] in stack map frame 错误
zhao_Gq
02-10 426
原因是集成了第三方sdk，在打包后出现的错误，但又不能修改第三方sdk。 经过搜索得知是proguard的一个bug，需修改源码中，ClassConstants.java类中的ATTR_StackMapTable的值改为"dummy"，然后重新编译一个proguard。 重新编译Proguard 1.官网下载源码https://www.guardsquare.com/en/products/...
混淆jar包 作为依赖工程 打包混淆出错 Unknown verification type [96] in stack map frame
wen243624708的专栏
08-23 3199
int i; private boolean test(){ boolean handled=false; if(i>0){ handled=false; }else{ handled=true; } handled=test1(i); return handled; } private boolean test1(int i){ return  i }
Android 混淆 Unknown verification type
水墨青花的专栏
01-23 3910
Android工程打包sdk，导出jar已被混淆，该jar被第三方使用，混淆时出现Unknown verification type [*] in stack map frame问题，测试发现 if(){ }else{ Log.cerateLog("something"); } 其中Log public class Log { public stati
Eclipse proguard 代码混淆 微信第三方库 Can\'t process class (Unknown verification type [95] in stack map frame)
doubleface999的博客
02-19 1179
今天编译一个android的Eclipse项目，不开启代码混淆能成功导出apk包，开启代码混淆后报错：[2016-12-26 23:45:51 - test] Proguard returned with error code 1. See console[2016-12-26 23:45:51 - test] java.io.IOException: Can't read [D:\xxx\tes
解决proguard混淆报错-Proguard5.1
04-27
proguard混淆jar包提示错误：Unknown verification type [*] in stack map frame 解决方案：找到proguard源码中proguard\src\proguard\classfile\ClassConstants.java类，然后修改ATTR_StackMapTable的值，将原来的...
解决Android开发中打包失败及ProGuard相关异常
studio\app\libs\libammsdk.jar]`以及`Can't process class [com/tencent/wxop/stat/al.class] (Unknown verification type [95] in stack map frame)`这类异常。该问题的根本原因与Java字节码验证机制、ProGuard...
android开发无法打包或打包出错
09-26
解决java.io.IOException: Can't read [D:\android_studio\app\libs\libammsdk.jar(;;;;;;!META-INF/MANIFEST.MF)] (Can't process class [com/tencent/wxop/stat/al.class] (Unknown verification type [95] in stack map frame))等无法打包问题， 解压后把android_sdk\tools\下的proguard整个替换。
Android 混淆打包时第三方jar包报错Unknown verification type [*] in stack map frame
g2285715的专栏
04-20 2783
小菜鸟表示项目快上线了，赶着出个包的时候遇到这个问题，简直是要了命。然而在国内的搜索结果99%都是在说proguard的源码中的ClassConstants.java中ATTR_StackMap属性改为dummy，然后还得ANT打包回去。看了顿时表示这么大工程量如果最后改了还是不行我是不是可以召唤草泥马神兽把作者给轮了。另外还有一种说法就是proguard的版本太低，看了下sdk/tools/pr
proguard 出现的“(Unknown verification type [XX] in stack map frame)”问题的解决办法
一叶扁舟江上游的博客
06-04 1508
这里写链接内容 在你依赖的外部jar包已经混淆的情况下再进行混淆打包有可能出现以下情况：Error:ProGuard: [UserCenter] java.io.IOException: Can’t read [F:\sources\iSDK\libs\libammsdk.jar] (Can’t process class [com/tencent/wxop/stat/al.class] (Unk
Can't process class [com/imagpay/bP.class] (Unknown verification type [25] in stack map frame
炽魂的世界
11-01 1901
最近在Android studio下打包文件，设置混淆后，打包出现 * What went wrong: Execution failed for task ':unionpaylib:transformClassesAndResourcesWithProguardForDebug'. > java.io.IOException: Can't read [D:\MPos\unionpayli
Android Studio打包时，已经混淆的jar文件报错(Unknown verification type [*] in stack map frame)
zhangnx
11-17 633
记录一个遇到很久的问题 项目本身是Unity3d的类型，打包的时候一直报错  “(Unknown verification type [*] in stack map frame)”  问题定位到 unity-class.jar； 百度后解决方案都是很统一，都指明出是proguard的一个bug，解决方案也清楚，是重新编译一个proguard。 首先肯定的是这个解
Android项目混淆问题 Unknown verification type [48] in stack map frame
HeartCircle的博客
09-25 558
近期在打包Android工程的时候遇到了混淆问题，不混淆的情况下怎么样都是好的，混淆时候打包就有问题，报错如下： [2018-09-19 13:14:49 - zplugin] Caused by: java.lang.RuntimeException: Unknown verification type [48] in stack map frame [2018-09-19 13:14:49...
Unknown verification type [17] in stack map frame
huwan.cn的博客
05-17 1136
Error:Execution failed for task ':app:transformClassesWithMultidexlistForDebug'.> java.io.IOException: Can't read [C:\Users\huwan\Desktop\ASCorporatePioneer\CorporatePioneer2\app\build\intermediates\t
list exhaustively the type of coverage in digital IC verification using systemverilog
最新发布
11-07
When using SystemVerilog for digital IC verification, the following types of coverage are commonly used: ### Code Coverage - **Line Coverage**: Measures whether each line of code in the design has been executed. It helps identify dead code that is never reached during simulation. ```systemverilog module example; reg a, b, c; always @(*) begin c = a & b; // Line to be covered end endmodule ``` - **Toggle Coverage**: Checks if signals in the design have changed their values. This is important for ensuring that all possible signal transitions are being exercised. ```systemverilog module toggle_example; reg clk; reg data; always @(posedge clk) begin data <= ~data; // Signal toggling end endmodule ``` - **Branch Coverage**: Determines if all possible branches in conditional statements (e.g., `if-else`, `case` statements) have been taken. ```systemverilog module branch_example; reg [1:0] sel; reg out; always @(*) begin case(sel) 2&#39;b00: out = 1&#39;b0; 2&#39;b01: out = 1&#39;b1; 2&#39;b10: out = 1&#39;b0; 2&#39;b11: out = 1&#39;b1; endcase end endmodule ``` - **Expression Coverage**: Evaluates if all possible combinations of expressions in the code have been computed. ### Functional Coverage - **Scenario Coverage**: Ensures that all defined functional scenarios of the design have been tested. For example, in a memory controller, scenarios could include read, write, burst read, and burst write operations. ```systemverilog covergroup mem_operations; coverpoint mem_cmd { bins read = {READ}; bins write = {WRITE}; bins burst_read = {BURST_READ}; bins burst_write = {BURST_WRITE}; } endgroup ``` - **Data Coverage**: Focuses on the range and combinations of data values used during verification. For instance, in a multiplier, different input data values should be tested. ```systemverilog covergroup multiplier_data; coverpoint a { bins small = {[0:10]}; bins medium = {[11:100]}; bins large = {[101:255]}; } coverpoint b; cross a, b; endgroup ``` ### Assertion Coverage - **Assertion Firing Coverage**: Measures whether assertions in the design have fired (either passed or failed). Assertions are used to check the correctness of the design&#39;s behavior. ```systemverilog module assertion_example; reg clk; reg reset; reg valid; assert property (@(posedge clk) valid |->!reset); cover property (@(posedge clk) valid |->!reset); endmodule ``` ### State Machine Coverage - **State Coverage**: Verifies that all states in a finite state machine (FSM) have been reached. ```systemverilog module fsm_example; reg clk; reg reset; typedef enum {S0, S1, S2} state_type; state_type state; always @(posedge clk or posedge reset) begin if (reset) state <= S0; else case(state) S0: state <= S1; S1: state <= S2; S2: state <= S0; endcase end covergroup fsm_coverage; coverpoint state; endgroup endmodule ``` - **State Transition Coverage**: Checks if all possible state transitions in the FSM have occurred.
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值