
In either case you may need to install extra packages on your camera:
Open a Terminal (e.g. in the Virtual Machine either in Eclipse or via the system).
1.
Open a ssh connection like (e.g. in Eclipse in the Virtual Machine you already have a connection):
ssh root@[IP ADDRESS OF YOUR MVBLUELYNX-X]
2.
Enter the root password
matrix
.
3.
Now, you have to install the gdbserver to debug remotely.
opkg update
opkg install gdbserver
4.
To install the native gdb application use:
opkg install gdb
5.
It is also recommended to install the following packets.
opkg install libthread-db1 glibc-dbg
6.
18.3.6.1 Debugging a sample on the mvBlueLYNX-X itself
To debug a program directly on the camera you have to install the
gdb
debugger on the mvBlueLYNX-X (see
above):
Important is the init file
.gdbinit
for the gdb-debugger. In this file set the path to libraries for the arm
crosscompiler/linker.
Example file
.gdbinit
:
set solib-search-path /usr/local/angstrom/arm/lib:
/usr/local/angstrom/arm/arm-angstrom-linux-gnueabi/lib
Separate Paths with ":" and write this command only in one line !
Setting the path to the file
.gdbinit
:
Run -> Debug Configurations -> Debugger -> GDB command file: .gdbinit
Now you can start
gdb
passing your application as the first parameter. The procedure is identical to using
gdb
on any other computer. Full documentation for gdb is available here at sourceware.org.
gdb
is most useful when:
your application has been compiled with debug symbols (e.g. compiler option
-ggdb
)
1.
your application uses no automatic optimization level (i.e. compiler option
-O0
)
2.
the source files for the application are available to the
gdb
(e.g. by using an NFS mounted directory
from your development system).
3.
If, when using gdb, you see the message warning: Unable to find libthread_db matching inferior's
thread library, thread debugging will not be available. Please install the recommended packages as
noted above.
18.3.6.2 Debugging a sample on the mvBlueLYNX-X remotely
To debug a program remotely you have to install the
gdbserver
on the mvBlueLYNX-X (see above):
Make a new run and debug configuration:
Open Run -> Run Configurations....
1.
mvBlueLYNX-X Technical Manual
160
22 April 2016 Version - 1.49
MATRIX VISION GmbH
Summary of Contents for mvBlueLYNX-X
Page 1: ...mvBlueLYNX X Technical Manual 22 April 2016 Version 1 49 Copyright 2017 MATRIX VISION GmbH...
Page 2: ......
Page 10: ...VIII...
Page 11: ...1 mvBlueLYNX X Technical Manual MATRIX VISION GmbH 22 April 2016 Version 1 49 1...
Page 12: ...mvBlueLYNX X Technical Manual 2 22 April 2016 Version 1 49 MATRIX VISION GmbH...
Page 22: ...mvBlueLYNX X Technical Manual 12 22 April 2016 Version 1 49 MATRIX VISION GmbH...
Page 24: ...mvBlueLYNX X Technical Manual 14 22 April 2016 Version 1 49 MATRIX VISION GmbH...
Page 27: ...mvBlueLYNX X Technical Manual MATRIX VISION GmbH 22 April 2016 Version 1 49 17...
Page 28: ...mvBlueLYNX X Technical Manual 18 22 April 2016 Version 1 49 MATRIX VISION GmbH...
Page 30: ...mvBlueLYNX X Technical Manual 20 22 April 2016 Version 1 49 MATRIX VISION GmbH...
Page 50: ...mvBlueLYNX X Technical Manual 40 22 April 2016 Version 1 49 MATRIX VISION GmbH...
Page 108: ...mvBlueLYNX X Technical Manual 98 22 April 2016 Version 1 49 MATRIX VISION GmbH...
Page 124: ...mvBlueLYNX X Technical Manual 114 22 April 2016 Version 1 49 MATRIX VISION GmbH...
Page 190: ...mvBlueLYNX X Technical Manual 180 22 April 2016 Version 1 49 MATRIX VISION GmbH...
Page 214: ...mvBlueLYNX X Technical Manual 204 22 April 2016 Version 1 49 MATRIX VISION GmbH...
Page 226: ...mvBlueLYNX X Technical Manual 216 22 April 2016 Version 1 49 MATRIX VISION GmbH...
Page 230: ...mvBlueLYNX X Technical Manual 220 22 April 2016 Version 1 49 MATRIX VISION GmbH...
Page 236: ...mvBlueLYNX X Technical Manual 226 22 April 2016 Version 1 49 MATRIX VISION GmbH...