Thread: [Announce] kernel-power stable v53 in Extras Testing
View Single Post
justmemory is offline justmemory
2019-01-24 , 10:34
Posts: 391 | Thanked: 908 times | Joined on Aug 2011 @ suncity
#126
Originally Posted by freemangordon View Post
gdb backtrace?
Run the earlier command and now the line changed to 25826...

Executing backtrace command inside gdb it says:

Code:
#0  0x40ff097c in raise () from /lib/libc.so.6
#1  0x40ff4b8c in abort () from /lib/libc.so.6
#2  0x40ff4b8c in abort () from /lib/libc.so.6
... and the line above continues till #98 where I skip it...

One other thing: I installed the previously built fcamera deb package to my other n900 which has libc version 2.5.1 and it runs without any issue... For me it is strange because that version was built against libc version 2.10 so I do not understand how can that be that it could run on that device if it does not on the other... As I understand from fcamera code it uses pthread, open, fprint and other libc6 related stuff but I can't imagine that would be a problem.

On the other side Halftux said that maybe i should compile other related packages (libjpeg62 for example) but I cannot find source for those... Should I try with debian versions...?


Update:// OK, I think I made a step forward (I do not understand what the errors might mean though - since I'm not very familiar with C language). In the FCam API (i.e. fcam-dev source) there are examples. So I simply gave the make command for example1 and run it. It did not gave glib errors but had the daemon setter creating error so I run it with gdb. The message from that is:
Code:
0x400649f0 in sem_wait () from /lib/libpthread.so.0
0x400649f0 <sem_wait+236>:      mov      r7,  r0
Backtrace info:
Code:
#0  0x400649f0 in sem_wait () from /lib/libpthread.so.0
#1  0x00023008 in FCam::TSQueue<FCam::N900::_Frame*>::pull()  ()
#2  0x0021ce8 in FCam::N900::Sensor::getFrame()  ()
#3  0x000b1d8 in main (argc=3, argv=0xbec184b4) at example1.cpp:42
Update2:// Maybe I'm total ridiculous but from the code and all... just like it could not handle the sensor of the n900...
Last edited by justmemory; 2019-01-24 at 13:35.
 

The Following User Says Thank You to justmemory For This Useful Post: