this should help us in near future:
* -valgrind[=MODE], to run under valgrind and toggle interesting
options as we often request users to give us valgrind logs but
they're often running valgrind on wrong binaries and with wrong
parameters. See enlightenment_start -help for more, but in sort:
-valgrind=all should give us enough information.
* -valgrind-log-file=path, so the log will not mix with lots of
output we do.
* debug: on crashes, always list traceback (execinfo/glibc
functions) and check if gdb exists, if so ask it to print out
traceback of all threads to stdout. gdb will be detached as soon
as messages were printed and everything should work without gdb as
well.
SVN revision: 41309
on my p4 3.4ghz + reiser3fs IO Wait time went from 2.6 to 1.9 seconds
(total login time went from 3.01511 to 2.29971, with 100% cached login time
being 0.41809)
on my core 2 duo laptop + ext3fs IO Wait time went from 2.05 to 1.15 seconds
(total login time went from 2.50988 to 1.60785, with 100% cached login time
being 0.45850)
this should speed up e's login a bit... i hope.
note - it is adaptive. it needs you to log in at least once using the current
code as it traps and logs certain file accesses and needs that log to replay
next login.
SVN revision: 26742
somewhere where its bin dir is not in $PATH and lib dir is not in ld.so.conf
OR in $LD_LIBRARY_PATH. this will quickly determine prefix set up 2 env vars
and launch e itself.
SVN revision: 21028
Sebastian Dransfeld
Christopher Michael
Gustavo Sverzut Barbieri
Carsten Haitzler
sebastid