>Summary of results so far:
>
>- This seems to be Linux-specific; Solaris and BSDI are not affected
>- This does not seem to be x86-specific
>- This does not seem to be gcc-version-specific
>- This may be proxy-related: different sequences or events will affect
> whether a crash occurs or not if a proxy is used; if a proxy is not
> used a crash apparently will not occur
>- This problem cannot be debugged using gdb
>- This problem is intermittent (not reliably reproducible)
Maybe it's one of that worst category of bugs, a stray pointer that
destroys data but the effect isn't felt until much later. Are there any
malloc debugging libraries we can link with? I used to like Purify
(proprietary) for this sort of problem.
This archive was generated by hypermail 2b29 : Wed Nov 15 2000 - 19:33:31 CST