Strange crash in glibc

Steve smorrey at gmail.com
Tue Mar 28 13:20:54 MST 2006


Yeah Electric Fence is what brought the issue to my attention, but
it's not giving me anything other than the fact that the issue exists.

On 3/28/06, Topher Fischer <javert42 at cs.byu.edu> wrote:
> Steve wrote:
> > Hmm valgrind segfaults?
> >
> [snip]
>
>
> > Any other ideas?
> >
> I would have said valgrind (compiling everything with -g of course), but
> apparently that won't work.  I've never used it before, but Electric
> Fence might be another option for detecting double-free's and other
> memory bugs.  I would guess that you'd want to compile with a -g in this
> case too.
>
> --
> Topher Fischer
> System Administrator - TMCB 1140
> GnuPG Fingerprint: 3597 1B8D C7A5 C5AF 2E19  EFF5 2FC3 BE99 D123 6674
> javert42 at cs.byu.edu
>
>
>
>
>
> /*
> PLUG: http://plug.org, #utah on irc.freenode.net
> Unsubscribe: http://plug.org/mailman/options/plug
> Don't fear the penguin.
> */
>
>
>



More information about the PLUG mailing list