On Thu, 13 Jan 2011 11:18:20 +0100
Michael Decker <[email protected]> wrote:
> 
> > * Fixed a bug in the GSM Gadget which caused a segfault of E
> I had E segfaults occasionally, often it correlated with running opkg
> update or opkg upgrade. Even though I can't really see the connection.
> Yesterday during the upgrade the same thing happened again.
> 

I am just guessing... but low RAM conditions?
opkg eats lots of RAM..
Then E tries to malloc'ate some memory, the operation fails.
E segfaults because it has failed to check for a non null result from malloc.

> 
> Thanks for your efforts,
> Michael
> _______________________________________________
> Shr-User mailing list
> [email protected]
> http://lists.shr-project.org/mailman/listinfo/shr-user


-- 
Visti Andresen
_______________________________________________
Shr-User mailing list
[email protected]
http://lists.shr-project.org/mailman/listinfo/shr-user

Reply via email to