| 1 |
On Tue, 26 Jul 2005, Willie Wong wrote: |
| 2 |
|
| 3 |
> I was away from my computer for one week, and so ran a massive update |
| 4 |
> on sunday night. After the update, on Monday morning, I woke up to |
| 5 |
> find my xsession ended with a message on the console that said |
| 6 |
> something to the effect that Enlightenment segfaulted, because some |
| 7 |
> supporting library tries to access memory that it shouldn't be |
| 8 |
> accessing. |
| 9 |
> |
| 10 |
> I dismissed it as enlightenment throwing a hissy fit. |
| 11 |
> |
| 12 |
> But the same thing happened again this morning. The problem is, I |
| 13 |
> don't quite know how to diagnose it. /var/log/Xorg.log only tells me |
| 14 |
> it caught sig 11 and will die. |
| 15 |
> |
| 16 |
> Honestly, I don't think running strace will be the best idea yet, I'd |
| 17 |
> like to save it as a last possibility, for the only reason that I |
| 18 |
> don't even know how to reproduce the crash. X was up and running |
| 19 |
> yesterday for over 14 hours, and enlightenment just crashed in the |
| 20 |
> middle of the night. |
| 21 |
> |
| 22 |
> So: what logs should I check and how should I find out what exactly |
| 23 |
> is causing the problem? |
| 24 |
> |
| 25 |
> W |
| 26 |
|
| 27 |
Disk full? |
| 28 |
df -h |
| 29 |
|
| 30 |
-- |
| 31 |
gentoo-user@g.o mailing list |
Archives