Welcome!

Welcome to the official BlackBerry Support Community Forums.

This is your resource to discuss support topics with your peers, and learn from each other.

inside custom component

Web and WebWorks Development


Thank you for visiting the BlackBerry Support Community Forums.

BlackBerry will be closing the BlackBerry Support Community Forums Device Forums on April 1st (Developers, see below)

BlackBerry remains committed to providing excellent customer support to our customers. We are delighted to direct you to the CrackBerry Forums, a well-established and thorough support channel, for continued BlackBerry support. Please visit http://forums.crackberry.com or http://crackberry.com/ask. You can also continue to visit BlackBerry Support or the BlackBerry Knowledge Base for official support options available for your BlackBerry Smartphone.

"When we launched CrackBerry.com 10 years ago, we set out to make it a fun and useful destination where BlackBerry Smartphone owners could share their excitement and learn to unleash the full potential of their BlackBerry. A decade later, the CrackBerry community is as active and passionate as ever and I know our knowledgeable members and volunteers will be excited to welcome and assist more BlackBerry owners with their questions."

- Kevin Michaluk, Founder, CrackBerry.com

Developers, for more information about the BlackBerry Developer Community please review Join the Conversation on the BlackBerry Developer Community Forums found on Inside BlackBerry.


Reply
Highlighted
Contributor
Posts: 44
Registered: ‎11-12-2012
My Device: BB 10 Dev Apha
My Carrier: -
Accepted Solution

Debugging the native part of a Webworks extension

Dear All,

is there a way to debug webworks extensions in order to discover runtime errors?

We often (and randomically) get the common loading error "Require Error Can't find

/usr/lib/etc. Library cannot be found" but we cannot manage how to discover more information about that...

Apart from the error itself, I sadly found out that debbuging is really a pain in this scenario..

Any help or tip from BB guys is really appreciated!

thanks a lot

 

-marco

 

Retired
Posts: 165
Registered: ‎09-24-2012
My Device: Passport
My Carrier: Bell

Re: Debugging the native part of a Webworks extension

Hi Marco, debugging Native Extensions is currently quite difficult, due to their hybrid nature.

 

I typically create a native C++ app first, get it to work, and then make it into a native extension. Have you tried that?

 

Cheers,

A

Contributor
Posts: 44
Registered: ‎11-12-2012
My Device: BB 10 Dev Apha
My Carrier: -

Re: Debugging the native part of a Webworks extension

Hi,

yes, we just started going in that direction.

Thanks a lot

 

-marco