Hi,
could you redo the same test, but with passing the following option
"no-sighandler",just to get the hole stack trace till the main function.?

it seems that the call inside the "input.c"  is done with corrupted pointer.

On Mon, Nov 24, 2008 at 6:48 PM, Страхиња Радић <[EMAIL PROTECTED]> wrote:

> Nigel Hsiung wrote:
> > I had the same problem with df_video.After i removed the no-vt it started
> correctly.
> > Sorry wasnt much of help as u've already tried ./dfbinfo.
>
>        I only used the --dfb:no-vt parameter following the advice I got
> from
> jw hu. I get signal 11 either way.
>
> haithem rahmani wrote:
> > hi,
> > since you are inlinux you can do the following:
> >
> >    1. build your application in debug mode.
> >    2. in the shell type "ulimit -c 8000" to set the size of the
> core file
> >    3. run your application and you'll get a message saying (core
> dumped)
> >    4. check your current working directory for a file nale "core" or
> >       "core.<PID>"
> >    5. now run: gdb "your_application_file" "the_core_file"
> >    6. let the gdb finish analyzing the core file
> >    7. type 'bt"
> >    8. you'll get the call satck and where your code crahshed>
> >
> > hope this will help.
>
>        Here's what I get:
>
> (gdb) bt
> #0  0xb8085424 in __kernel_vsyscall ()
> #1  0x0017d740 in raise () from /lib/libc.so.6
> #2  0x0017f108 in abort () from /lib/libc.so.6
> #3  0xb7f97845 in signal_handler (num=11, info=0xbf88409c, foo=0xbf88411c)
>     at signals.c:413
> #4  <signal handler called>
> #5  0xb802324a in init_devices (core=0x98b2fb8) at input.c:1169
> #6  0xb8023912 in dfb_input_core_initialize (core=0x98b2fb8,
> data=0x98b3220,
>     shared=0x98b16e0) at input.c:385
> #7  0xb8011c59 in dfb_core_part_initialize (core=0x98b2fb8,
>     core_part=0xb806ca40) at core_parts.c:73
> #8  0xb801126c in dfb_core_initialize (core=0x98b2fb8) at core.c:983
> #9  0xb801146d in dfb_core_arena_initialize (arena=0x0, ctx=0x98b2fb8)
>     at core.c:1060
> #10 0xb7fa97c1 in fusion_arena_enter (world=0x98b3008,
>     name=0xb805f7ea "DirectFB/Core",
>     initialize=0xb8011350 <dfb_core_arena_initialize>,
>     join=0xb8010ff0 <dfb_core_arena_join>, ctx=0x98b2fb8,
> ret_arena=0x98b2fc8,
>     ret_error=0xbf8846e8) at arena.c:509
> #11 0xb8010ca1 in dfb_core_create (ret_core=0xbf884728) at core.c:338
> #12 0xb7fc0ecb in DirectFBCreate (interface=0x804b414) at directfb.c:193
> #13 0x080487e7 in main (argc=1, argv=0xbf8847f4) at dfbinfo.c:92
>
>        I configured DirectFB with the command:
>
> ./configure --with-inputdrivers=keyboard,joystick,ps2mouse
> --with-gfxdrivers=nvidia --prefix=/usr --enable-debug
>
> --
>   _     _   ______________________________________________________
>  /(_____)\ | ____ __  __ __ __                                    |
>  \_/~ ~\_/ |/ __// /_/ // // /  http://www.gnu.org/home.sr.html   |
>   (\'_'/)  / /  / __  /_\ ' /  http://www.stallman.org            |
>    (o_o)  /_/  /_/ /_//____/  http://alas.matf.bg.ac.yu/~mr99164  |
>            |______________________________________________________|
> _______________________________________________
> directfb-users mailing list
> directfb-users@directfb.org
> http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users
>
_______________________________________________
directfb-users mailing list
directfb-users@directfb.org
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users

Reply via email to