New issue
Advanced search Search tips

Issue 764468 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: Sep 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

GetSigtrampRange DCHECKs always on 10.11

Project Member Reported by a...@chromium.org, Sep 12 2017

Issue description

10.11.6 (15G1611)

I always get

[33270:1295:0912/153905.448096:FATAL:native_stack_sampler_mac.cc(339)] Check failed: info.start_ip == address (140735348958457 vs. 140735348958480)
0   libbase.dylib                       0x00000001231ee04e base::debug::StackTrace::StackTrace(unsigned long) + 174
1   libbase.dylib                       0x00000001231ee10d base::debug::StackTrace::StackTrace(unsigned long) + 29
2   libbase.dylib                       0x00000001231ec3bc base::debug::StackTrace::StackTrace() + 28
3   libbase.dylib                       0x000000012328bcdf logging::LogMessage::~LogMessage() + 479
4   libbase.dylib                       0x0000000123289645 logging::LogMessage::~LogMessage() + 21
5   libbase.dylib                       0x00000001233bf53f base::(anonymous namespace)::GetSigtrampRange(unsigned long*, unsigned long*) + 447

on every launch.

It's 0x7FFF807B64F9 vs 0x7FFF807B6510.
 

Comment 1 by lgrey@chromium.org, Sep 12 2017

Weird. Any chance you could you mail me libsystem_platform.dylib from that machine?

Comment 2 by a...@chromium.org, Sep 12 2017

This really makes no sense. It seems that it's counting from __sigunaltstack.
Screen Shot 2017-09-12 at 3.45.21 PM.png
119 KB View Download

Comment 3 by lgrey@chromium.org, Sep 12 2017

dwarfdump says:
start_addr: 0x0000000000002510 __sigtramp

So it seems like libunwind is falling down somewhere

Comment 4 by lgrey@chromium.org, Sep 13 2017

For posterity: 10.11 indeed seems to be pulling info for __sigunaltstack. Adding 1 to sigtramp's address to avoid the boundary condition seems to work, so that's the planned workaround.

Comment 5 by lgrey@chromium.org, Sep 14 2017

Forgot to add this bug to https://chromium-review.googlesource.com/c/chromium/src/+/665501

Should be fixed at ToT

Comment 6 by a...@chromium.org, Sep 14 2017

Status: Verified (was: Assigned)
Confirmed.

Sign in to add a comment