如何调试黑莓验证错误？ [英] How to debug a blackberry verification error?

问题描述

我得到的是：

  

模块我的应用已验证
  错误XXXX偏移1646

其中根据<一href=\"http://www.blackberry.com/knowledgecenterpublic/livelink.exe/fetch/2000/348583/796557/800708/800647/Support_-_MIDlet_has_verification_error_at_offset.html?nodeid=800711&vernum=0\"相对=nofollow>黑莓，包含了是没有用第三方developpers的信息。

我在buglog（与'catfail'选项）看，而我上发现它坠毁，不知其所以然的方法。有趣的是，当我从我的应用程序中删除这个方法，但它仍然记录有关导致错误的方法相同。这是一种奇怪的。

额外的信息：我的应用程序包含LWUIT和blackberryport

我也看过<一个href=\"http://www.blackberry.com/knowledgecenterpublic/livelink.exe/fetch/2000/348583/800332/832062/Support_-_$p$pventing_verification_errors.html?nodeid=1499031&vernum=0\"相对=nofollow> KB文章DB-00744 ，这表明验证错误，可能意味着以下任何'14'的错误。它是随机的，或者是有这种逻辑背后的方法？

解决方案

  

我在buglog（与'catfail'选项）看，而我上发现它坠毁，不知其所以然的方法。有趣的是，当我从我的应用程序中删除这个方法，但它仍然记录有关导致错误的方法相同。这是一种奇怪的。

您必须在您的构建/部署/测试过程的某个地方犯了一个错误....假设你正在谈论的应用程序本身的工作方法有关的，不仅仅是一些方法，你的应用程序调用。再次尝试做这一切。

  

它是随机的？或者是他们的这种逻辑背后的方法？

人们会认为，这些已发现的与黑莓平台的不同版本不同的客户应用验证错误作出贡献的所有问题。它说虽然这几个人似乎有点奇怪。例如不必要的进口（3）应该是无害的，用包私人错误地（4）将导致Java编译错误...我还以为。而且我不喜欢这样的事实，该清单往往不说的为什么的这些措施可能是必要的。

这本说明来看，我的感觉是一些在黑莓开发工具链的工具被设计相当差。 （当然，它不可能是的是的难以验证，生产信息的诊断，而不是无证内部错误codeS，还有一些提到闻之类的解决方法错误的事。）

All I get is:

"Module 'my-app' has verification error 'xxxx' at offset '1646'

Which according to blackberry, contains information that is of no use to third party developpers.

I looked in the buglog (with the 'catfail' option), and all I found was a method on which it crashed, not why. funny thing is, when I remove this method from my application, it still logs the same method for causing the error. It's kind of strange.

extra info: My app contains LWUIT, and the blackberryport

I've also read the KB article DB-00744, which suggest a verification error can mean any of the following '14' errors. Is it random, or is there a method behind this logic?

解决方案

I looked in the buglog (with the 'catfail' option), and all I found was a method on which it crashed, not why. funny thing is, when I remove this method from my application, it still logs the same method for causing the error. It's kind of strange.

You must have made a mistake somewhere in your build / deploy / test process .... assuming that you are talking about one of your application's own methods, not just some method that your application calls. Try doing it all again.

Is it random? or is their a method behind this logic?

One would assume that these are all issues that have been found to contribute to in verification errors with various customer apps on various releases of the Blackberry platform. It be said though that a couple of them seem a bit odd. For instance unnecessary imports (3) should be harmless, and using "package private" incorrectly (4) should cause Java compilation errors ... I'd have thought. And I don't like the fact that the list often don't say why these measures might be necessary.

Judging from this note, I get the feeling that some of the tools in the Blackberry development toolchain are rather poorly engineered. (Surely it cannot be that hard for the verifier to produce informative diagnostics instead of undocumented "internal" error codes. And some of the things mentioned "smell" like workarounds for bugs.)

这篇关于如何调试黑莓验证错误？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！