7 replies to this topic

[globis]

Hi all,


What openpli developpers use to debug enigma1 source code ?
is it possible to use gdb and how to implement it.


Regards,

[pieterg]

enigma is too large for gdb to handle, so no, I haven't had much luck with it. (if I remember correctly, backtracing coredumps works however).

So it's back to good old printf's
(actually shouldn't hurt the eventual quality of the code, not being able to use gdb, usually results in giving weird constructions a bit more thought, instead of just 'see whether it works')

[Sjaaky]

I tried to use gdb on enigma 1, but it resulted in segfaults all over the place. It was not useable in any way.

[globis]

Can you give more details about using printf !
how to connect dreambox with serial cable, with software to backtrace, is there any config, ...

[Sjaaky]

You don't need to. Just kill enigma and start it in the console (with a telnet connection). All debug output appears on stdout/stderr.

printf doesn't support backtrace .

[pcd]

In the c++ code put in eDebug statements.

For enigma1 - telnet commands :-

killall rcS
killall enigma
enigma>/tmp/enigma.log 2>&1 &

Cheers, pcd.

[globis]

Thanks, got it !

Another question:

Is it possible to recompile only enigma and flash it on the box, because "make image" or "bitbake dreambox-image" is taking so much time.

so any solution to flash enigma without rebuilding/flashing the whole root_fs ??

[pieterg]

bitbake -f -c compile -b ../openembedded/packages/enigma/enigma.bb
and copy the resulting binary to the box