search for: optimized_out

Hi all, The debug entry values feature introduces new DWARF symbols (tags, attributes, operations) on caller (call site) as well as on callee side; and the intention is to improve debugging user experience by using the functionality (especially in “optimized” code by turning “<optimized_out>” values into real values). The call site information includes info about call itself (described with DW_TAG_call_site) with corresponding children representing function arguments at the call site (described with DW_TAG_call_site_params). The most interesting DWARF attribute for us (here) is DW_...

...s been generated following the instructions found at : https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace Strangely, I'm absolutely sure that the DONT_OPTIMIZE flag is properly set (I recompiled Asterisk from scratch, making sure this was enabled), you will still see some "<optimized_out>" values. Should I post this on the asterisk-dev mailing-list, or directly into the issue tracker ? Thanks ! Hoggins!

..., > > The debug entry values feature introduces new DWARF symbols (tags, attributes, > operations) on caller (call site) as well as on callee side; and the intention > is to improve debugging user experience by using the functionality (especially > in “optimized” code by turning “<optimized_out>” values into real values). The > call site information includes info about call itself (described with > DW_TAG_call_site) with corresponding children representing function arguments > at the call site (described with DW_TAG_call_site_params). The most interesting > DWARF attribute...