mirror of
https://github.com/Zenithsiz/ftmemsim-valgrind.git
synced 2026-02-03 10:05:29 +00:00
Small comment fix: .h specifies "all frames", implementation uses 8.
Two fixes could be done: Either we fix the comments or we increase N_FRAMES to be rather VG_DEEPEST_BACKTRACE. We fix the comment for the following reason: This is (at least for the moment) not performance critical. as this is only called when an error is reported. However, searching for local vars is extremely costly. It is unlikely that an error is reported for a stack variable which is more than 8 frames deeper than theframe in which it is detected. So, fix the comment, waiting for a complaint that a deeper variable is not properly described. git-svn-id: svn://svn.valgrind.org/valgrind/trunk@13235
This commit is contained in:
parent
d62fe23131
commit
1fcd318239
@ -3171,7 +3171,7 @@ Bool consider_vars_in_frame ( /*MOD*/XArray* /* of HChar */ dname1,
|
||||
}
|
||||
|
||||
/* Try to form some description of DATA_ADDR by looking at the DWARF3
|
||||
debug info we have. This considers all global variables, and all
|
||||
debug info we have. This considers all global variables, and 8
|
||||
frames in the stacks of all threads. Result is written at the ends
|
||||
of DNAME{1,2}V, which are XArray*s of HChar, that have been
|
||||
initialised by the caller, and True is returned. If no description
|
||||
|
||||
@ -96,7 +96,7 @@ extern Bool VG_(get_datasym_and_offset)( Addr data_addr,
|
||||
/*OUT*/PtrdiffT* offset );
|
||||
|
||||
/* Try to form some description of DATA_ADDR by looking at the DWARF3
|
||||
debug info we have. This considers all global variables, and all
|
||||
debug info we have. This considers all global variables, and 8
|
||||
frames in the stacks of all threads. Result is written at the ends
|
||||
of DNAME{1,2}V, which are XArray*s of HChar, that have been
|
||||
initialised by the caller, and True is returned. If no description
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user