ProDBG icon indicating copy to clipboard operation
ProDBG copied to clipboard

Breakpoint filtering based on callstack

Open emoon opened this issue 11 years ago • 2 comments

Breakpoint filtering based on callstack, e.g. don't break in the future from this callstack. Also, break only with current callstack from now on.

emoon avatar Feb 08 '13 12:02 emoon

Also, the ability to use locals from stack-frames above the location of the breakpoint in conditional BPs, if the callstacks match (or at least match up to that point where the local variable you want to use is declared).

rhm avatar Nov 22 '14 19:11 rhm

That is a great suggestion.

Right now I think the only way to do this (seeing from the backend point of view)

Break at breakpoint Check callstack If string != in callstack, continue else stay While this should work it will likely slowdown the program a bit (as it needs to stop, check callstack, each time it passes the breakpoint)

Do you think that would be acceptable?


Yeah totally. I think people more or less expect this :) It still beats getting a 100 BPs and manually looking at the callstack! :) Also if you only get like a 100 over for ex. 20 sec the overheadt would be next to nothing.

Also, it would also be nice to do filtering on path-names of files in callstack. Last week I needed to get a BP when some middleware called a function in our engine, but we called the function from within the engine a lot too - so being able to include/exclude on src-path would be great as well.


Yeah. Both filtering on file/path and name in callstack would be very easy to add so I see no problem with that.

emoon avatar Apr 24 '16 16:04 emoon