>>> * 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. Hm, that would sort of make sense. But I also have an additional 128M swapfile, so I would not expect a RAM shortage so soon. I'm not talking about opkg downloading tons of new packages. E has already crashed on me when there was nothing to update at all and nothing was downloaded.
Michael _______________________________________________ Shr-User mailing list [email protected] http://lists.shr-project.org/mailman/listinfo/shr-user
