I googled how to follow forked processes see the attached session.
If you do this you should be able to find your bug,

 -o d-i 
/home/memmel/GTK2.7/Qspin/Developer/Source/Debian/Source/DebianInstaller/main-menu
GNU gdb Red Hat Linux (6.3.0.0-1.21rh)
Copyright 2004 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 "i386-redhat-linux-gnu"...Using host
libthread_db library "/lib/libthread_db.so.1".

(gdb) set follow-fork-mode
Requires an argument. Valid arguments are child, parent.
(gdb) set follow-fork-mode child
(gdb) run -o d-i
/home/memmel/GTK2.7/Qspin/Developer/Source/Debian/Source/DebianInstaller/main-menu
Starting program:
/media/WDC_Combo/home/memmel/GTK2.7/Qspin/Developer/Source/Debian/Source/DebianInstaller/debconf
-o d-i 
/home/memmel/GTK2.7/Qspin/Developer/Source/Debian/Source/DebianInstaller/main-menu
Reading symbols from shared object read from target memory...done.
Loaded system supplied DSO at 0xe22000
[Thread debugging using libthread_db enabled]
[New Thread -1208478016 (LWP 14942)]

       ---------------------- DirectFB v0.9.23 ---------------------
             (c) 2000-2002  convergence integrated media GmbH
             (c) 2002-2004  convergence GmbH
        -----------------------------------------------------------

(*) DirectFB/Core: Single Application Core. (2005-07-21 22:02)
(*) Direct/Memcpy: Using MMXEXT optimized memcpy()
[New Thread 27016112 (LWP 14945)]
(*) Direct/Thread: Running 'SDL Input' (INPUT, 14945)...
 (!!!)  *** UNIMPLEMENTED [fusion_reactor_set_lock] *** [reactor.c:802]
(*) DirectFB/Input: SDL Input 0.1 (Denis Oliver Kropp)
(*) DirectFB/Genefx: MMX detected and enabled
(*) DirectFB/Graphics: MMX Software Rasterizer 0.6 (convergence
integrated media GmbH)
(*) DirectFB/Core/WM: Default 0.2 (Convergence GmbH)
[New Thread 52087728 (LWP 14946)]
(*) Direct/Thread: Running 'EventBufferFeed' (MESSAGING, 14946)...

(debconf:14942): Gdk-DirectFB-WARNING **:
gdk_display_request_selection_notification Unimplemented function


(debconf:14942): Gdk-DirectFB-WARNING **: gdk_window_set_keep_above()
not implemented.


(debconf:14942): Gdk-DirectFB-WARNING **: gdk_window_set_keep_below()
not implemented.

Attaching after fork to child process 14947.

Program received signal SIGSEGV, Segmentation fault.
[Switching to process 14947]
0x08049068 in main (argc=149692544, argv=0x21) at debconf.c:138
138     debconf.c: No such file or directory.
        in debconf.c
(gdb)


On 7/28/05, Mike Emmel <[EMAIL PROTECTED]> wrote:
> Okay  it looks like a bug outside of gtk Davide and I got a standalone dev env
> its attached.
> Bottom line is it looks like its outside the gtk code at least now.
> I've got no idea what going on with the forked process etc etc.
> I've never attached gdb through forks but it looks like one of the
> child process crashed prob not the frontend.
> 
> In short I don't see what I can do to help here except  I do note that
> mutiple frontends are supported do the otheres work.
> Failing that a few printfs to track the initialization of the gtk
> fronted so you could attach and break in the debugger before the crash
> is possible. I'm not in a position to build.  If the bug is only in
> the gtk frontend then printfs and commenting out code can isolate the
> problem area so you know where to attach the debugger thats what I
> have to do.
> 
> Mike
> 
> 
> Here is and important email
> Hi Mike,
> I should mention that last night I did not find what the cause of the crash
> is, but I managed
> to grab an interesting gdb backtrace; atm I'm at work and I don't have it.
> last night I posted it on the #debian-boot IRC channel, and here is a message
> that could be interesting
> 
> http://lists.debian.org/debian-boot/2005/07/msg01014.html
> 
> let me know if you managed to start debconf
> 
> 
> Here is the trace
>        ---------------------- DirectFB v0.9.23 ---------------------
>              (c) 2000-2002  convergence integrated media GmbH
>              (c) 2002-2004  convergence GmbH
>         -----------------------------------------------------------
> 
> (*) DirectFB/Core: Single Application Core. (2005-07-21 22:02)
> (*) Direct/Memcpy: Using MMXEXT optimized memcpy()
> [New Thread 27106224 (LWP 14601)]
> (*) Direct/Thread: Running 'SDL Input' (INPUT, 14601)...
>  (!!!)  *** UNIMPLEMENTED [fusion_reactor_set_lock] *** [reactor.c:802]
> (*) DirectFB/Input: SDL Input 0.1 (Denis Oliver Kropp)
> (*) DirectFB/Genefx: MMX detected and enabled
> (*) DirectFB/Graphics: MMX Software Rasterizer 0.6 (convergence
> integrated media GmbH)
> (*) DirectFB/Core/WM: Default 0.2 (Convergence GmbH)
> [New Thread 66788272 (LWP 14602)]
> (*) Direct/Thread: Running 'EventBufferFeed' (MESSAGING, 14602)...
> 
> (debconf:14598): Gdk-DirectFB-WARNING **:
> gdk_display_request_selection_notification Unimplemented function
> 
> 
> (debconf:14598): Gdk-DirectFB-WARNING **: gdk_window_set_keep_above()
> not implemented.
> 
> 
> (debconf:14598): Gdk-DirectFB-WARNING **: gdk_window_set_keep_below()
> not implemented.
> 
> Detaching after fork from child process 14604.
> 
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread -1208772928 (LWP 14598)]
> 0x00000000 in ?? ()
> (gdb) bt
> #0  0x00000000 in ?? ()
> #1  0x006d2379 in frontend_delete (obj=0x9fed348) at frontend.c:208
> #2  0x08048a30 in cleanup () at debconf.c:41
> #3  0x08048abf in sighandler (sig=17) at debconf.c:65
> #4  <signal handler called>
> #5  0x00fd8402 in __kernel_vsyscall ()
> #6  0x0080bd3b in __read_nocancel () from /lib/libc.so.6
> #7  0x006cf833 in confmodule_communicate (mod=0xa0f2a20) at confmodule.c:77
> #8  0x0804918a in main (argc=4, argv=0xbf85f134) at debconf.c:153
> (gdb) quit
> 
> 
> 
> 
> On 7/27/05, Mike Emmel <[EMAIL PROTECTED]> wrote:
> > On 7/27/05, Attilio Fiandrotti <[EMAIL PROTECTED]> wrote:
> > > since i'm very interested in the debugging of the frontend, could you
> > > add me in the cc list?
> >
> > Sure no problem your on for me.   At the moment nothing happening I'm 
> > missing
> >
> >         linux-gate.so.1 =>  (0x00815000)
> >         libdebconf.so => not found
> >         libdl.so.2 => /lib/libdl.so.2 (0x00357000)
> >         libc.so.6 => /lib/libc.so.6 (0x00205000)
> >         /lib/ld-linux.so.2 (0x001e7000)
> >         libdebian-installer.so.4 => not found
> >
> > And want the source for the gtk part.
> >
> > Mike
> >
> >
> > I'm currently missing these libs
> >
> >
> > >
> > > thanks
> > >
> > > attilio
> > > Mike Emmel wrote:
> > > > On 7/27/05, Davide Viti <[EMAIL PROTECTED]> wrote:
> > > >
> > > >>I recompiled DirectFB with --enable-debug=yes
> > > >>here are some more details:
> > > >>
> > > >>http://www.webalice.it/zinosat/dfb_2.7_dbgen2.png
> > > >>http://www.webalice.it/zinosat/dfb_2.7_dbgen.png
> > > >>
> > > >>hope this helps,
> > > >>Davide
> > > >>
> > > >
> > > > Yep you crashed :(
> > > >
> > > > I've got your app I'll try and run it.
> > > >
> > > > This is the last time I'll cc the list we can just continue with 
> > > > private emails.
> > > > Mine is [EMAIL PROTECTED] if its not showing for you.
> > > >
> > > > Mike
> > > >
> > > > _______________________________________________
> > > > directfb-dev mailing list
> > > > [email protected]
> > > > http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
> > > >
> > >
> > >
> >
> 
> 
>

_______________________________________________
directfb-dev mailing list
[email protected]
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev

Reply via email to