Closed GoogleCodeExporter closed 9 years ago
Hi,
the problem came up in the helper directory, that is there to compile 32bit
version of liblinuxtrack, so my guess is that you didn't install gcc-multilib
package...
Once you install it, the header should be there...
As for the v4l2, thanks for the point - I'm working on a fix and I'll check it
in as soon as I check it is working.
Kind regards,
Michal
Original comment by f.jo...@email.cz
on 22 Oct 2011 at 3:56
That did the trick! I was looking at an outdated version of the install
instructions, and had expected configure to fail if dependencies were missing.
Works great with my TrackIR 5 and TrackClip Pro. Thanks for making this happen!
By the way, when I hit "Discard Changes" in ltr_gui after starting the camera,
the program segfaults. Backtrace is:
#0 0x0000000000000000 in ?? ()
#1 0x00007fff9218a511 in ltr_int_read_blobs_tir (blt=0x7fff92b90db0, min=4,
max=500, img=0x7fff92b90d50) at tir_img.c:288
#2 0x00007fff9218a78a in ltr_int_tracker_get_frame (ccb=0x7ffff7ddbc60,
f=0x7fff92b90db0) at tir_driver.c:98
#3 0x00007fff9218aa84 in ltr_int_rl_run (ccb=0x7ffff7ddbc60,
cbk=0x7ffff7bd2f54 <frame_callback>) at runloop.c:48
#4 0x00007ffff7bc91e1 in ltr_int_cal_run (ccb=0x7ffff7ddbc60,
cbk=0x7ffff7bd2f54 <frame_callback>) at cal.c:81
#5 0x00007ffff7bd2fd3 in cal_thread_fun (param=0x0) at ltlib_int.c:31
#6 0x00007ffff4229efc in start_thread ()
from /lib/x86_64-linux-gnu/libpthread.so.0
#7 0x00007ffff37c389d in clone () from /lib/x86_64-linux-gnu/libc.so.6
#8 0x0000000000000000 in ?? ()
Additionally, as I was typing this
Original comment by Ral...@gmail.com
on 23 Oct 2011 at 10:09
Whoops. hit submit too early.
As I was typing that message the first time, and trying to reproduce the bug,
my system locked up hard, with only the mouse cursor responsive. I'm not
certain that the events are related, and have no idea how to find out more, but
the timing is suspicious.
The segfault I described occurs when the tracking is operational. If it's
stopped, no crash occurs. If it's paused, a crash occurs when it's resumed.
Additionally, when the program segfaults, the camera is left on (judging by the
status indicators); I'm not sure this is important, but it seems like it should
be shut down cleanly.
Finally, the FPS display frequently displays invalid numbers (-2147483648 seems
to be a favorite).
Original comment by Ral...@gmail.com
on 23 Oct 2011 at 10:17
Hi,
thanks for the report, I just committed new revision, that should disable
Discard changes button while tracking is active (Defaults button already does
that).
Also the FPS indication should behave well (stupid uninitialized variable ;).
As for the Track IR active when ltr_gui crashes, it is unfortunately normal for
now - the camera needs explicit shutdown and it doesn't happen when crash
occurs. For now the workaround is either to start ltr_gui and start and stop
tracking, or to unplug and replug TrackIR...
I'm thinking of adding some signal handlers, to handle those situations but I
still have to think this through...
As for the lock-up, I sincerely hope it was not caused by linuxtrack - so far I
didn't get any similar reports (only on guy reported system lockups but under
different circumstances and with different symptoms). Anyway I don't know about
any way how linuxtrack could cause this.
Thank you for your help,
Michal
Original comment by f.jo...@email.cz
on 23 Oct 2011 at 8:07
Original comment by f.jo...@email.cz
on 4 Nov 2011 at 6:54
Original issue reported on code.google.com by
Ral...@gmail.com
on 22 Oct 2011 at 2:19Attachments: