On Sun, 2006-01-15 at 12:05 -0500, Justin Pryzby wrote:
> Could you try to run it under valgrind? This might show invalid
> memory accesses or some such which would be useful. (It will be slow,
> though).
Running it under valgrind did not show anything useful. In fact, i
wasn't able to reproduce the bug. Because of this behaviour, I examined
the startup script, and found out that if i comment out these 3 lines:
#if type "${FIREFOX_DSP}" > /dev/null 2>&1; then
# MOZ_PROGRAM="${FIREFOX_DSP} ${MOZ_PROGRAM}"
#fi
the bug disappears. $FIREFOX_DSP is esddsp on my system, so I think the
problem is there. Feel free to reassign this bug.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
