On Wed, Jul 8, 2009 at 5:33 PM, Alan Carvalho de Assis<acassis@gmail.com> wrote:
Hi All,
I am trying to port Dillo to i.MX27 (ARM9) processor. Using LTIB build system (www.ltib.org) to cross-compile FLTK.
I cross-compiled FLTK2, but it is crashing, I can't run any demo example.
To FLTK1.3 everything works fine, I ran all examples successfully.
To FLTK2 nothing works. I searched Internet for similar error, but nothing solves it.
I tested these FLTK revision: fltk-2.0.x-r6793 fltk-2.0.x-r6101
It appears to crash at "fltk::setfont". In fact I can see "bad font: fixed" message just before that "Segmentation Fault".
Could someone give me some suggestion to solve this issue?
See below the gdb backtrace. I am running gdbserver on i.MX27 board (IP 192.168.0.180)
Best Regards,
Alan
$ arm-elf-gdb /home/alan/ltib/rootfs/home/test/hello GNU gdb 6.6 Copyright (C) 2006 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. ?Type "show warranty" for details. This GDB was configured as "--host=i686-pc-linux-gnu --target=arm-linux"... (gdb) target remote 192.168.0.180:3333 Remote debugging using 192.168.0.180:3333 warning: Unable to find dynamic linker breakpoint function. GDB will be unable to debug shared library initializers and track explicitly loaded dynamic code. 0x400007e0 in ?? () (gdb) set solib-absolute-prefix /home/alan/ltib/rootfs (gdb) b main Breakpoint 1 at 0xb9e8: file hello.cxx, line 9. (gdb) c Continuing.
Breakpoint 1, main (argc=1, argv=0xbeaa5e44) at hello.cxx:9 9 ? ? ? ? Window *window = new Window(300, 180); (gdb) c Continuing.
Program received signal SIGSEGV, Segmentation fault. 0x4025dfe0 in strcmp () from /home/alan/ltib/rootfs/lib/libc.so.6 (gdb) bt #0 ?0x4025dfe0 in strcmp () from /home/alan/ltib/rootfs/lib/libc.so.6 #1 ?0x0000d1e4 in fltk::setfont (font=0x3a0ac, psize=12) at x11/Font_xlfd.cxx:542 #2 ?0x0001ac80 in fltk::Widget::draw_box (this=0x40b68, r=@0xbeaa5a18) at Widget_draw.cxx:94 #3 ?0x0001acc0 in fltk::Widget::draw_box (this=0x0) at Widget_draw.cxx:88 #4 ?0x0001a810 in fltk::Widget::draw (this=0x0) at Widget.cxx:644 #5 ?0x0000d618 in fltk::Group::draw_child (this=<value optimized out>, w=@0x40b68) ? ?at Group.cxx:750 #6 ?0x0000e218 in fltk::Group::draw (this=0x406e0) at Group.cxx:682 #7 ?0x00013ff8 in fltk::Window::flush (this=0x406e0) at x11/run.cxx:2566 #8 ?0x000116d4 in fl_window_flush (window=0x406e0) at run.cxx:657 #9 ?0x00011784 in fltk::flush () at run.cxx:691 #10 0x00016a60 in fltk::wait (time_to_wait=1.00000002e+20) at run.cxx:484 #11 0x00016b8c in fltk::run () at run.cxx:397 #12 0x402071cc in __libc_start_main () from /home/alan/ltib/rootfs/lib/libc.so.6 #13 0x0000b94c in _start () (gdb)
_______________________________________________ Dillo-dev mailing list Dillo-dev@dillo.org http://lists.auriga.wearlab.de/cgi-bin/mailman/listinfo/dillo-dev
I'd probably encourage you to file a FLTK2 bug upstream or send an email to FLTK mailing list, however w.r.t FLTK2 I don't think they will fix it soon anyway. My POV is that they answer to bug reports but not fixing much. Michal