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

[via llvm-bugs]

https://bugs.llvm.org/show_bug.cgi?id=44300

Reid Kleckner <rnk at google.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |DUPLICATE
             Status|NEW                         |RESOLVED
                 CC|                            |rnk at google.com

--- Comment #1 from Reid Kleckner <rnk at google.com> ---
I loaded the minidump in windbg, and it's our old friend, line zero. This was
what `k` produced after configuring symbol server search paths and reloading
the symbols:

 # Child-SP          RetAddr           Call Site
00 00000056`38d5ef68 00007ffc`e0391118 ntdll!NtWaitForSingleObject+0xa
01 00000056`38d5ef70 00007ffc`ad711210 KERNELBASE!WaitForSingleObjectEx+0x94
02 00000056`38d5f010 00007ffc`ad70fcba
chrome_child!base::WaitableEvent::TimedWait+0x100
[c:\b\s\w\ir\cache\builder\src\base\synchronization\waitable_event_win.cc @
107] 
03 00000056`38d5f0c0 00007ffc`ad70fbe6
chrome_child!base::MessagePumpDefault::Run+0x7a
[c:\b\s\w\ir\cache\builder\src\base\message_loop\message_pump_default.cc @ 57] 
04 00000056`38d5f140 00007ffc`ad70f56e
chrome_child!base::sequence_manager::internal::ThreadControllerWithMessagePumpImpl::Run+0x86
[c:\b\s\w\ir\cache\builder\src\base\task\sequence_manager\thread_controller_with_message_pump_impl.cc
@ 463] 
05 00000056`38d5f190 00007ffc`aeee29ea chrome_child!base::RunLoop::Run+0x1ae
[c:\b\s\w\ir\cache\builder\src\base\run_loop.cc @ 158] 
06 00000056`38d5f230 00007ffc`ad6fa9e5 chrome_child!content::UtilityMain+0x1d2
[c:\b\s\w\ir\cache\builder\src\content\utility\utility_main.cc @ 150] 
07 00000056`38d5f420 00007ffc`ad6e1e47
chrome_child!content::ContentMainRunnerImpl::Run+0x1a9
[c:\b\s\w\ir\cache\builder\src\content\app\content_main_runner_impl.cc @ 874] 
08 00000056`38d5f5f0 00007ffc`ad6e18cb chrome_child!service_manager::Main+0x4b4
[c:\b\s\w\ir\cache\builder\src\services\service_manager\embedder\main.cc @ 423] 
09 00000056`38d5f8a0 00007ffc`ad6e1485 chrome_child!content::ContentMain+0x3e
[c:\b\s\w\ir\cache\builder\src\content\app\content_main.cc @ 19] 
0a 00000056`38d5f930 00007ff7`f5da2bdf chrome_child!ChromeMain+0x125
[c:\b\s\w\ir\cache\builder\src\chrome\app\chrome_main.cc @ 0] 
0b 00000056`38d5fa20 00000056`38ff9100 chrome!MainDllLoader::Launch+0x177
[c:\b\s\w\ir\cache\builder\src\chrome\app\main_dll_loader_win.cc @ 202] 


The key line is:
chrome_child!ChromeMain+0x125 [....\chrome_main.cc @ 0]


I think we fixed this in LLVM 9d8f0b3519c4e9e4e2a3d3b19ea0caf9ef3f85ce (Oct
10). The crash you linked is from Chrome M78, which seems to have branched in
September. So, it was built with a compiler that lacks the fix to avoid
emitting line zero locations.

I think we can say that this is a duplicate of issue 43530.

*** This bug has been marked as a duplicate of bug 43530 ***

-- 
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/20200104/55a779ce/attachment.html>