[llvm-bugs] [Bug 44300] New: Bad source/line debug information for one address in Chrome

via llvm-bugs llvm-bugs at lists.llvm.org
Fri Dec 13 14:56:58 PST 2019


            Bug ID: 44300
           Summary: Bad source/line debug information for one address in
           Product: clang
           Version: trunk
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: enhancement
          Priority: P
         Component: C++
          Assignee: unassignedclangbugs at nondot.org
          Reporter: brucedawson at chromium.org
                CC: blitzrakete at gmail.com, dgregor at apple.com,
                    erik.pilkington at gmail.com, llvm-bugs at lists.llvm.org,
                    richard-llvm at metafoo.co.uk

In crash/df2293b94ced16ae on the main thread (not the thread that crashed) most
of the stack entries lead to the correct source code but the entry for >       
chrome_child.dll!ChromeMain does not. In the windbg "kc" output this is the
function between ContentMain and Launch:

09 chrome_child!content::ContentMain
0a chrome_child!ChromeMain
0b chrome!MainDllLoader::Launch

To see the behavior you have to have symbol server enabled (of course) and also
source indexing. This lets VS or windbg download the source code, which it does
for all other functions on the stack.

In fact the debuggers download chrome_main.cc but then refuse to use it. The VS
source search information says:

Locating source for 'c:\b\s\w\ir\cache\builder\src\chrome\app\chrome_main.cc'.
(No checksum.)
The file 'c:\b\s\w\ir\cache\builder\src\chrome\app\chrome_main.cc' does not
Looking in script documents for
The debugger found source in the following locations:
1: c:\src\chromium3\src\chrome\app\chrome_main.cc (No checksum.)
(No checksum.)
The debugger will use the source at location 1.

This sounds familiar but I can't tell what is going on. I don't know how VS
found the source code that windbg downloaded, why it didn't find the source
code that it downloaded, and why it decided to use the repo copy of the source
code which is almost certainly wrong.

You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20191213/8f4fd373/attachment-0001.html>

More information about the llvm-bugs mailing list