[Ves] Debugging VES

[Pat Marion]

Hi Sishir,

You can run ctest with -VV to get full output to see why the program is
crashing.

For debugging, as I said in my previous email, set the cmake variable
CMAKE_BUILD_TYPE to Debug, then rebuild.  That will compile VES and VTK
with debug symbols.  An Android.mk file shouldn't be required.  I haven't
personally done gdb debugging on jni code through eclipse, so unfortunately
I cannot guide you any further.

Pat

On Wed, Mar 14, 2012 at 11:51 AM, Sishir Jain <sishirjain at gmail.com> wrote:

> Hi,
>     I was able to built ves using Mesa. But on running ctest I got the
> following error:
>
> ========================================================================
> root at ubuntu:~/VES/Apps/Linux/CMakeBuild/build/CMakeExternals/Build/ves-host#
> ctest
> Test project
> /root/VES/Apps/Linux/CMakeBuild/build/CMakeExternals/Build/ves-host
>     Start 1: TestDrawPlane
> 1/7 Test #1: TestDrawPlane ....................***Exception: SegFault
> 0.53 sec
>     Start 2: TestKiwiViewer
> 2/7 Test #2: TestKiwiViewer ...................***Exception: SegFault
> 1.80 sec
>     Start 3: TestClipPlane
> 3/7 Test #3: TestClipPlane ....................***Exception: SegFault
> 0.40 sec
>     Start 4: TestTexture
> 4/7 Test #4: TestTexture ......................***Exception: SegFault
> 0.31 sec
>     Start 5: TestGradientBackground
> 5/7 Test #5: TestGradientBackground ...........***Exception: SegFault
> 0.45 sec
>     Start 6: TestPointCloud
> 6/7 Test #6: TestPointCloud ...................***Exception: SegFault
> 0.46 sec
>     Start 7: TestMatrix
> 7/7 Test #7: TestMatrix .......................   Passed    0.00 sec
>
> 14% tests passed, 6 tests failed out of 7
>
> Total Test time (real) =   6.98 sec
>
> The following tests FAILED:
>       1 - TestDrawPlane (SEGFAULT)
>       2 - TestKiwiViewer (SEGFAULT)
>       3 - TestClipPlane (SEGFAULT)
>       4 - TestTexture (SEGFAULT)
>       5 - TestGradientBackground (SEGFAULT)
>       6 - TestPointCloud (SEGFAULT)
> Errors while running CTest
>
>
> =======================================================================================
>
> Apart from this error, I am also unable to create a project/workspace
> using which I can debug ves. Normally an android project using native code
> through jni is debugged by attaching the native source files under jni
> folder and using ndk-build to create .so and then ndk-gdb for debugging.
> Android.mk is required in this case.
>
> If instead of Android.mk, cmake is to be used for building, could you
> please guide in creating a project/workspace where ves can be debugged and
> extended (preferably on eclipse) ?
>
> Regards,
> Sishir
>
>
> On Mon, Mar 12, 2012 at 11:29 PM, Pat Marion <pat.marion at kitware.com>wrote:
>
>> Hi Sishir,
>>
>> Rather than use Android.mk to build VES, I recommend you stick with the
>> regular cmake + makefiles build.  In cmake, you can configure the
>> CMAKE_BUILD_TYPE variable to be Debug, or RelWithDebInfo, this will build
>> ves with debug information so that it can be debugged by ndk-gdb when
>> linked to your project.
>>
>> For you build error when configuring the build for linux, you are missing
>> GLESv2.  I install this on ubuntu using the mesa package: libgles2-mesa-dev
>>
>> Please send your questions to the VES public mailing list so that others
>> can participate.
>>
>> Pat
>>
>>
>> On Sun, Mar 11, 2012 at 8:31 AM, Sishir Jain <sishirjain at gmail.com>wrote:
>>
>>> Hi Pat,
>>>           We need to build our own android application using ves. We
>>> were trying to generate an android project in which we could use native
>>> C/C++ ves code through jni.
>>>  We wanted to include the ves souce files in the same project and debug
>>> that using ndk debugger (ndk-gdb). But we got stuck at the make file
>>> (Android.mk) which should include the information about the ves files.
>>>
>>> We also tried building ves for testing on linux but could not (see
>>> attachment).
>>>
>>> We need your help to configure the development environment (eclipse or
>>> anything else which you may prefer) where we could change ves C/C++ source.
>>>
>>> Regards,
>>> Sishir
>>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/ves/attachments/20120314/b3353067/attachment-0002.html>