<div dir="ltr"><div>Hi Ben,</div><div><br></div><div>I didn't have a chance to debug the scripts yet, but just in case you missed my last email with examples of repeatable blocks</div><div>and sequences - do you think we still need to analyze further, will the scripts tell more about the heap?</div><div><br></div><div>Thanks,</div><div>Oleg</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Feb 28, 2019 at 10:14 PM Ben Pfaff <<a href="mailto:blp@ovn.org">blp@ovn.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Tue, Feb 26, 2019 at 01:41:45PM +0400, Oleg Bondarev wrote:<br>
> Hi,<br>
> <br>
> thanks for the scripts, so here's the output for a 24G core dump:<br>
> <a href="https://pastebin.com/hWa3R9Fx" rel="noreferrer" target="_blank">https://pastebin.com/hWa3R9Fx</a><br>
> there's 271 entries of 4MB - does it seem something we should take a closer<br>
> look at?<br>
<br>
I think that this output really just indicates that the script failed.<br>
It analyzed a lot of regions but didn't output anything useful. If it<br>
had worked properly, it would have told us a lot about data blocks that<br>
had been allocated and freed.<br>
<br>
The next step would have to be to debug the script. It definitely<br>
worked for me before, because I have fixed at least 3 or 4 bugs based on<br>
it, but it also definitely is a quick hack and not something that I can<br>
stand behind. I'm not sure how to debug it at a distance. It has a<br>
large comment that describes what it's trying to do. Maybe that would<br>
help you, if you want to try to debug it yourself. I guess it's also<br>
possible that glibc has changed its malloc implementation; if so, then<br>
it would probably be necessary to start over and build a new script.<br>
</blockquote></div></div>