You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think it would be nice if analyze_malloc() could (optionally) store the source code from the line being analysed in its MallocInfo result struct. I've just written a work-around that requires opening and searching through the source files, but analyze_malloc_files has basically already done this, since the source lines are in the .mem files. The option for additional lines of context would be nice too. Maybe something like a keyword argument context, default value 0 (current behaviour), 1 adds the source code line, 2 includes +/-1 line of context, etc.
The text was updated successfully, but these errors were encountered:
I think it would be nice if
analyze_malloc()
could (optionally) store the source code from the line being analysed in itsMallocInfo
result struct. I've just written a work-around that requires opening and searching through the source files, butanalyze_malloc_files
has basically already done this, since the source lines are in the.mem
files. The option for additional lines of context would be nice too. Maybe something like a keyword argumentcontext
, default value0
(current behaviour),1
adds the source code line,2
includes +/-1 line of context, etc.The text was updated successfully, but these errors were encountered: