Improve test_zeroize.gdb breakpoint
Improve the position of the breakpoint to be set at a line of code that is less likely to be optimised out by the compiler. Setting the breakpoint at a place that can be easily optimised out by the compiler will cause the gdb script to fail as it cannot match the source code line to the compiled code. For this reason the breakpoint is now set at the fclose() call which is very unlikely to be optimised out or there might be a resource leak.
This commit is contained in:
parent
b1262a3bdb
commit
24768bfa37
1 changed files with 1 additions and 1 deletions
|
@ -17,7 +17,7 @@
|
|||
|
||||
set confirm off
|
||||
file ./programs/test/zeroize
|
||||
break zeroize.c:90
|
||||
break zeroize.c:88
|
||||
|
||||
set args ./programs/test/zeroize.c
|
||||
run
|
||||
|
|
Loading…
Reference in a new issue