search for: addlt

...t even know what should be the correct location information for *bar*. However, in this case, since the conditional instruction that clobbers *r4* is a function return, I'd expect to read the value of *bar* from *r4* in the remaining of the function. If the conditional instruction *poplt *was *addlt r4, r0, 3* for example, what should be the correct location list of *bar*? For now, my only idea is to check if the clobbering MI is a *conditional return* in *DbgValueHistoryCalculator* which computes the end address of a location llist entry. But I do not feel like this is the correct fix though...

...the program. Debug information that is only accurate for some paths is a bug. A serious bug, because if the user can't rely on the debug info to be correct in some cases, they can't rely on any of the debug info to be correct. -- adrian > > If the conditional instruction poplt was addlt r4, r0, 3 for example, what should be the correct location list of bar? > > For now, my only idea is to check if the clobbering MI is a conditional return in DbgValueHistoryCalculator which computes the end address of a location llist entry. But I do not feel like this is the correct fix tho...

...s through the program. Debug information that is only accurate for some paths is a bug. A serious bug, because if the user can't rely on the debug info to be correct in some cases, they can't rely on any of the debug info to be correct. -- adrian If the conditional instruction poplt was addlt r4, r0, 3 for example, what should be the correct location list of bar? For now, my only idea is to check if the clobbering MI is a conditional return in DbgValueHistoryCalculator which computes the end address of a location llist entry. But I do not feel like this is the correct fix though. Look...

...because if the user can't rely on the debug info to be correct in *some* >> cases, they can't rely on *any* of the debug info to be correct. >> >> >> >> -- adrian >> >> >> >> >> >> If the conditional instruction *poplt *was *addlt r4, r0, 3* for >> example, what should be the correct location list of *bar*? >> >> >> >> For now, my only idea is to check if the clobbering MI is a * >> conditional return* in *DbgValueHistoryCalculator* which computes the >> end address of a location lli...

...for some paths is a bug. A serious bug, > because if the user can't rely on the debug info to be correct in *some* > cases, they can't rely on *any* of the debug info to be correct. > > > > -- adrian > > > > > > If the conditional instruction *poplt *was *addlt r4, r0, 3* for example, > what should be the correct location list of *bar*? > > > > For now, my only idea is to check if the clobbering MI is a * conditional > return* in *DbgValueHistoryCalculator* which computes the end address of > a location llist entry. But I do not feel...

...for some paths is a bug. A serious bug, because if the user can't rely on the debug info to be correct in some cases, they can't rely on any of the debug info to be correct. > > > > -- adrian > > > > > > > If the conditional instruction poplt was addlt r4, r0, 3 for example, what should be the correct location list of bar? > > > > For now, my only idea is to check if the clobbering MI is a conditional return in DbgValueHistoryCalculator which computes the end address of a location llist entry. But I do not feel like this is the co...