warn users when no line# info: adopt "<nosyms>" marker on windows to match linux?

[derekbruening]

From bruen...@google.com on October 20, 2011 14:10:29

for users who forget to build w/ debug info, or for callstacks in system libs, it can be very misleading to have callstacks based only on export symbols with no line #s whatsoever.

Maybe should add an explicit message "No debug info found: recompile your application with debug info to get line numbers".

should ensure it fires w/ cygwin g++-compiled app.
add cygwin1.dll warning too?

on linux I've long had a "" marker after the module name so that
same convention could be carried over to windows:

Error #1: UNADDRESSABLE ACCESS: reading 1 byte(s)
#0 unopt!main
#1 libc.so.6!__libc_start_main [/build/buildd/eglibc-2.11.1/csu/libc-start.c:226]
#2 unopt!_start
Note: refers to 3 byte(s) into memory that was freed here:
Note: # 0 unopt!main
Note: # 1 libc.so.6!__libc_start_main [/build/buildd/eglibc-2.11.1/csu/libc-start.c:226]
Note: # 2 unopt!_start

Original issue: http://code.google.com/p/drmemory/issues/detail?id=635

[derekbruening]

From bruen...@google.com on December 08, 2011 08:04:07

this will also make it easier to interpret callstacks w/ system libraries from the bots that don't have symbols

Owner: rnk@google.com

[derekbruening]

From bruen...@google.com on December 20, 2011 10:48:53

alternatively could do the mod+offs when no syms (mentioned in issue #290 )
in either case, don't put into suppression.txt.
and if someone pastes from error report to make supp: more likely to
include accidentally than to include +offs esp if in sep column

also xref issue #603

[derekbruening]

From rnk@google.com on December 20, 2011 15:51:50

This issue was closed by revision r684 .

Status: Fixed