During development, it is useful to have mechanism to start Taint Analysis from particular frame and to explicitly set Tainted location to track. This patch adds following command line arguments to support that:
Option -start-crash-order=<unsigned> to specify crash-order of the frame where TA should start
Option start-taint-reg=<register-name> to specify register name for simple register location or base register for memory location
Option start-taint-offset=<int> to specify offset for memory location
The test from this patch reproduces problem where frame is missing from the backtrace, which prevents successful crash analysis. However, by using the newly added options, we could find the correct blame line.
During development, it is useful to have mechanism to start Taint Analysis from particular frame and to explicitly set Tainted location to track. This patch adds following command line arguments to support that:
-start-crash-order=<unsigned>to specify crash-order of the frame where TA should startstart-taint-reg=<register-name>to specify register name for simple register location or base register for memory locationstart-taint-offset=<int>to specify offset for memory locationThe test from this patch reproduces problem where frame is missing from the backtrace, which prevents successful crash analysis. However, by using the newly added options, we could find the correct blame line.