Summary: | Provide more callstacks on memory pool related errors | ||
---|---|---|---|
Product: | [Developer tools] valgrind | Reporter: | Matthias Schwarzott <zzam> |
Component: | memcheck | Assignee: | Julian Seward <jseward> |
Status: | REPORTED --- | ||
Severity: | normal | CC: | 8e3b3cde, lange, philippe.waroquiers, pjfloyd, tilkax |
Priority: | NOR | ||
Version: | 3.9.0.SVN | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: |
Show callstacks of rellocated block in mempool
Show callstacks of reallocated block in mempool |
Description
Matthias Schwarzott
2013-07-11 19:37:11 UTC
Created attachment 81065 [details]
Show callstacks of rellocated block in mempool
Show two more callstacks for reallocated in mempool case.
Run the testcase cli_req also with --keep-stacktraces=alloc-and-free
Only filter_stderr does delete a bit too much of the callstacks so this should be fixed.
Created attachment 86853 [details]
Show callstacks of reallocated block in mempool
Updated the patch after the refactoring of rev 13965.
Maybe even more info could be extracted (offset+size of the inner block etc.).
It seems this will not be merged because it enlarges the struct _AddrInfo, of which quite a few are allocated at runtime. (In reply to Matthias Schwarzott from comment #3) > It seems this will not be merged because it enlarges the struct _AddrInfo, > of which quite a few are allocated at runtime. Sorry, info given on irc yesterday was for another patch. Growing (reasonably) struct _AddrInfo is not a problem, as we have very few of these. It is struct _MC_Chunk which is more memory critical. So, it is not hopeless to have this merged. Philippe I ran into this issue, and the message "bytes inside a recently re-allocated block of size alloc'd" is rather puzzling. This patch helped me tracking the issue behind it and I would like this to be merged, as this is really required to track issues when using custom mempools |