When benchmarking certain snippets that access memory, segmentation
faults are a very real possibility if the memory annotations are not
perfect. These situtations are currently difficult to debug as there is
no indication of which addresses need to be mapped. This patch adds in
support for printing the address a segmentation fault occurred at to
make it easier to gather this information.
Details
Details
Diff Detail
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
Comment Actions
I've structured this as a different class of error rather than as a SnippetCrash with the address inside a string as I intend to use this in a downstream basic block annotator application and need programatic access to the address at which the segmentation fault occurred.
Comment Actions
It looks like we'll have to implement such an escape for any crash type that client code wants to handle. Have you considered keeping only SnipetCrash, but storing si_signo and si_addr there ?
clang-format not found in user’s local PATH; not linting file.