Required by (0)

Sources (2)

Latest Comments

p.janeck commented on 2015-02-14 15:40

Last but not least... I found the bug. In the file Graspit/src/graspitGUI.cpp in the method: GraspItGUI::processArgs(int argc, char** argv) (~ line 147)
change the line starting with:
while((c=getopt(argc, argv, "r:w:o:b:")) != EOL) {
to
while(int(c=getopt(argc, argv, "r:w:o:b:")) != 255) {
This could be a bug in the armv7h glibc implementation. If no argument is given it does not return a char but the value 11111111. This could be different on other systems.
You can check the value of getopt() with std::bitset<CHAR_BIT>(c) and adjust your version.

Cheers,
Peter

p.janeck commented on 2015-02-14 15:32

Last but not least... I found the bug. In the file Graspit/src/graspitGUI.cpp in mathod: GraspItGUI::processArgs(int argc, char** argv) (~ line 147)
change the line starting with:
while(int(c=getopt(argc, argv, "r:w:o:b:")) != 255) {

p.janeck commented on 2015-02-14 15:32

Last but not least... I found the bug. In the file Graspit/src/graspitGUI.cpp in mathod: GraspItGUI::processArgs(int argc, char** argv) (~ line 147)
change the line starting with:
while(int(c=getopt(argc, argv, "r:w:o:b:")) != 255) {

p.janeck commented on 2015-01-18 21:47

OK, the debug thing seems not to be the problem. I can run the binary by itself but not through the bash script in /usr/bin. I added the to "export" lines from /usr/bin/graspit to my ~/.bashrc and symlinked the binary from /usr/share/graspit to /usr/bin.
This is just a quick fix, although it works.

Any ideas why the application isn't running from the bash script?

Btw. I installed graspit an an x86_64 maschine and it runs just fine without any fixing.

Regards,
Peter

p.janeck commented on 2015-01-18 17:17

I successfully compiled the graspit binary on my chromebook with armv7h architecture. Nevertheless, the programm won't run. It just shows the start dialog and gives no output on the console. When I run gdb on the binary it just tells me:

Program received signal SIGILL, Illegal instruction.
0x76fdfb24 in _dl_debug_initialize () from /lib/ld-linux-armhf.so.3

Is there a way to get more information from the binary to trck down the error?