On Sun, 2007-08-19 at 17:42 +0200, Jean-Marc Beaune wrote:
> Hi,
> 
> Did you emerge --depclean, revdep-rebuild and dispatch-conf after
> emerging world ?
> 
> I had seg fault with all my applications after emerging a new package
> (Kino), and that did the trick.
> 
> /JM
> 

Hi, Thanks Jean-Marc,

I just did the depclean and revdep-rebuild, and dispach-conf, and I
still get the segfault.

Here is the error:

This GDB was configured as "i686-pc-linux-gnu".
(gdb) 
(gdb) file /usr/bin/f4l 
Reading symbols from /usr/bin/f4l...(no debugging symbols found)...done.
Using host libthread_db library "/lib/libthread_db.so.1".
(gdb) exec-file /usr/bin/f4l 
(gdb) run /usr/bin/f4l 
Starting program: /usr/bin/f4l /usr/bin/f4l
(no debugging symbols found)
Failed to read a valid object file image from memory.
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1222756688 (LWP 8773)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1222756688 (LWP 8773)]
0x08069a55 in ?? ()

The splash screen shows up, but that is it.
Any advice?

Thanks again!
rick



-- 
[EMAIL PROTECTED] mailing list

Reply via email to