On Mon, Feb 29, 2016 at 12:17:13AM +0000, Patrick O'Callaghan wrote:
> On Sun, 2016-02-28 at 19:13 -0500, Fred Smith wrote:
> > This is weird, because it has hardly even been "yum update"-ed during
> > the interval. what would have changed? I dunno...
>
> RAM problem? Try memchk.
not outside the realm of the possible,... but I wouldn't expect it to
cause only a single program to crash, and ALWAYS with the same set
of clicks/keystrokes, without fail. after installing a ton of
-debug packages and watching it in the debugger, it always segfaults
at the same place, and for a given set of actions with t he same
stack trace (the trace varies depending on which actions I did, but
for a single set of actions its always the same).
In fact, it dies in malloc.c, after a call from (I think it is named)
dv_freep or something ending with "freep", making me think that the
pointer being freed has been hosed (its not null), or something has
walked all over the malloc chain's bookkeeping.
Fred
--
---- Fred Smith -- fredex@xxxxxxxxxxxxxxxxxxxxxx -----------------------------
The eyes of the Lord are everywhere,
keeping watch on the wicked and the good.
----------------------------- Proverbs 15:3 (niv) -----------------------------
--
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
