English (United Kingdom)

https://curated-unify.zendy.io/wp-json/zendy-region/v1/featured_content/oa?rat=en

https://curated-unify.zendy.io/wp-json/zendy-region/v1/highlighted_journal/

Global: Zendy Plus annual

Presents the access of premium content as premium feature

Premium Content

Presents the keyphrase highlighting as premium feature

Keyphrase Highlighting

Presents the summarisation as premium feature

Summarisation

Insights

Presents the pdf analysis as premium feature

PDF Analysis

Presents the zaia usage as premium feature

ZAIA

Global: Zendy Plus monthly

Global: Zendy Tools annual

Global: Zendy Tools monthly

Global: Zendy Free Plan

The availability of debug information for optimized executables can largelyease crucial tasks such as crash analysis. Source-level debuggers use thisinformation to display program state in terms of source code, allowing users toreason on it even when optimizations alter program structure extensively. A fewrecent endeavors have proposed effective methodologies for identifyingincorrect instances of debug information, which can mislead users by presentingthem with an inconsistent program state.  In this work, we identify and study a related important problem: thecompleteness of debug information. Unlike correctness issues for which anunoptimized executable can serve as reference, we find there is no analogousoracle to deem when the cause behind an unreported part of program state is anunavoidable effect of optimization or a compiler implementation defect. In thisscenario, we argue that empirically derived conjectures on the expectedavailability of debug information can serve as an effective means to exposeclasses of these defects.  We propose three conjectures involving variable values and study how oftensynthetic programs compiled with different configurations of the popular gccand LLVM compilers deviate from them. We then discuss techniques to pinpointthe optimizations behind such violations and minimize bug reports accordingly.Our experiments revealed, among others, 24 bugs already confirmed by thedevelopers of the gcc-gdb and clang-lldb ecosystems.

Where Did My Variable Go? Poking Holes in Incomplete Debug Information