bug-texinfo
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [bug #48463] segmentation fault


From: mtsio
Subject: Re: [bug #48463] segmentation fault
Date: Thu, 14 Jul 2016 15:58:00 +0000

I think I discovered what causes the crash. In apropos_in_all_indices
(indices.c) at line 605 we are freeing up some memory (free
(this_fb->contents;). If I delete these lines it works correctly but
what is the root cause of that I'm not sure. The closer I got is that
when the address of win->node->contents is 'close' to this_fb->contents
and we free the second one we also messing up with win->node->contents.
If the info file we search for is big these two could overlap.

Is something like that possible?

If I delete these lines it does not crash but since you can't reproduce
it I think more people need to test my guess.

Gavin Smith:
> On 12 July 2016 at 10:26, mtsio <address@hidden> wrote:
>> I tested it with info from SVN.
>>
>> Attached the debug info with -x 3. I think though it's not very
>> accurate. I ran info gith gdb and the last files info searched was
>> gnash_user and gnash_ref.
> 
> You're right, this log doesn't tell us anything.
> 
> I notice some memory leaks when doing some testing, so I am going to
> try to fix those anyway.
> 
>> Maybe the bug is about preparing/showing the results of apropos not
>> about the search itself.
> 
> I suggest trying "info gettext" followed by searching in the index of
> the file, like "Igettext RET". That could be a simpler way to get a
> segmentation fault so would be easier to investigate. If not, it could
> be hard to get to the root of this.
> 

Attachment: fix-segmentation-fault-bug-48463.patch
Description: Text Data


reply via email to

[Prev in Thread] Current Thread [Next in Thread]