Re: [gentoo-user] Enlightenment segfaults?

[Willie Wong]

Some more observations to my problem:

   1. If, after I started X, I leave it overnight in a vc, then
   nothing bad happens. 

   2. But, if I leave it overnight in the X session, something
   crashes. 

Here's what I get from logging: 

---------begin snip----------
X Window System Version 6.8.2
Release Date: 9 February 2005
X Protocol Version 11, Revision 0, Release 6.8.2
Build Operating System: Linux 2.6.11-hardened-r1 i686 [ELF] 
Current Operating System: Linux sep 2.6.11-hardened-r1 #4 Sat Apr 2 21:44:14 EST
 2005 i686
Build Date: 28 June 2005
        Before reporting problems, check http://wiki.X.Org
        to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Tue Jul 26 16:44:04 2005
(==) Using config file: "/etc/X11/xorg.conf"
Using vt 7
Could not init font path element /usr/share/fonts/local/, removing from list!
Could not init font path element /usr/share/fonts/twmoefonts/, removing from lis
t!
xscreensaver: 16:44:09: running xscreensaver-gl-helper: Permission denied
No running windows found

(firefox-bin:6680): Gdk-WARNING **: gdk_property_get(): length value has wrapped
 in calculation (did you pass G_MAXLONG?)
SetGrabKeysState - disabled
SetGrabKeysState - enabled
ESD: error writing - Bad file descriptor
ESD: error writing - Bad file descriptor
No running windows found

(firefox-bin:1156): Gdk-WARNING **: gdk_property_get(): length value has wrapped
 in calculation (did you pass G_MAXLONG?)
SetGrabKeysState - disabled
SetGrabKeysState - enabled
SetGrabKeysState - disabled
SetGrabKeysState - enabled
No running windows found

(firefox-bin:5094): Gdk-WARNING **: gdk_property_get(): length value has wrapped
 in calculation (did you pass G_MAXLONG?)
SetGrabKeysState - disabled

   *** If unresolved symbols were reported above, they might not
   *** be the reason for the server aborting.

Fatal server error:
Caught signal 11.  Server aborting


Please consult the The X.Org Foundation support 
         at http://wiki.X.Org
 for help. 
Please also check the log file at "/var/log/Xorg.0.log" for additional informati
on.

XIO:  fatal IO error 104 (Connection reset by peer) on X server ":0.0"
      after 14989358 requests (14989349 known processed) with 0 events remaining
.
XIO:  fatal IO error 104 (Connection reset by peer) on X server ":0.0"
      after 5108892 requests (5108890 known processed) with 0 events remaining.
The application 'firefox-bin' lost its connection to the display :0.0;
most likely the X server was shut down or you killed/destroyed
the application.
X connection to :0.0 broken (explicit kill or server shutdown).
X connection to :0.0 broken (explicit kill or server shutdown).
X connection to :0.0 broken (explicit kill or server shutdown).
X connection to :0.0 broken (explicit kill or server shutdown).
X connection to :0.0 broken (explicit kill or server shutdown).
xinit:  connection to X server lost.
firefox-bin exited with non-zero status (1)
XIO:  fatal IO error 104 (Connection reset by peer) on X server ":0.0"
      after 14113208 requests (14113199 known processed) with 0 events remaining
.
X connection to :0.0 broken (explicit kill or server shutdown).
Enlightenment caused Segment Violation (Segfault)

This means that Enlightenment or support library routines it calls
have accessed areas of your system's memory that they are not
allowed access to. This is most likely a bug. It is recommended to
restart now. If you wish to help fix this please compile
Enlightenment with debugging symbols in and run Enlightenment
under gdb so you can backtrace for where it died and send in a
useful bug report with backtrace information and variable
dumps etc.
[27369] SessionExit already in progress ... now exiting
------------------end snip---------------------

I understand that this is probably not much information  about how to
solve my problem. But is there any suggestions on what I should do 
next?

The problem is that I don't even know now whether it is enlightenment
causing the segfault or not, since it appears that it happens 
after X has shutdown....

W


On Tue, Jul 26, 2005 at 12:59:15PM -0400, Willie Wong wrote:
> I was away from my computer for one week, and so ran a massive update
> on sunday night. After the update, on Monday morning, I woke up to
> find my xsession ended with a message on the console that said
> something to the effect that Enlightenment segfaulted, because some
> supporting library tries to access memory that it shouldn't be
> accessing.
>
> I dismissed it as enlightenment throwing a hissy fit.
>
> But the same thing happened again this morning. The problem is, I
> don't quite know how to diagnose it. /var/log/Xorg.log only tells me
> it caught sig 11 and will die.
>
> Honestly, I don't think running strace will be the best idea yet, I'd
> like to save it as a last possibility, for the only reason that I
> don't even know how to reproduce the crash. X was up and running
> yesterday for over 14 hours, and enlightenment just crashed in the
> middle of the night.
>
> So: what logs should I check and how should I find out what exactly
> is causing the problem?
>
> W
> --
> Computer games don't affect kids, I mean if Pac Man affected us as kids, we'd
> be sitting around in darkened rooms munching pills and listening to repetitive
> music.
> Sortir en Pantoufles: up 1 day, 16:24
> --
> gentoo-user@g.o mailing list

-- 
It was recently reported  in eWeek that "A senior Microsoft Corp. 
executive told a federal court last week that sharing information 
with competitors could damage national security and even threaten 
the U.S. war effort in Afghanistan. He later acknowledged that 
some Microsoft code was so flawed it could not be safely disclosed."
The Follow Up from Microsoft says "As a result of the flaws, Microsoft 
has asked the court to allow a "national security" carve-out from the 
requirement that any code or API's be made public. Microsoft has 
therefore taken the position that their code is so bad that it must
kept secret to keep people from being killed by it."
    ~Guacamoelefoo, /. 05-20-2002
Sortir en Pantoufles: up 3 days, 19:34
-- 
gentoo-user@g.o mailing list