Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

runtime: darwin/arm lldb needs to pass SIGSEGV #10043

Closed
crawshaw opened this issue Mar 1, 2015 · 3 comments
Closed

runtime: darwin/arm lldb needs to pass SIGSEGV #10043

crawshaw opened this issue Mar 1, 2015 · 3 comments
Milestone

Comments

@crawshaw
Copy link
Member

crawshaw commented Mar 1, 2015

The darwin/arm builder runs programs via lldb. (It is the only way to remotely dial the device running the binary.) The debugger likes to intercept signals that Go needs for normal operation. For example, there is a hidden panic inside the html/template tests that jams lldb. The obvious command does not work:

process handle SIGSEGV --stop false --pass true --notify false

It looks like passing on these signals may not be supported yet:

http://lists.cs.uiuc.edu/pipermail/lldb-dev/2013-July/002009.html

@minux
Copy link
Member

minux commented Mar 1, 2015 via email

@crawshaw
Copy link
Member Author

crawshaw commented Mar 1, 2015

I tried that manually. Giving lldb a continue instruction does not seem to work. (Even several times.)

crawshaw added a commit that referenced this issue Mar 3, 2015
Issue #10043

Change-Id: I6ce7f303cd96ac575f7a673dd4a459339382d22e
Reviewed-on: https://go-review.googlesource.com/6692
Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
@crawshaw crawshaw self-assigned this Mar 4, 2015
@crawshaw
Copy link
Member Author

LLDB engineer says its a long standing OS X bug and recommends we work around it:

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

@mikioh mikioh changed the title builder: darwin/arm lldb needs to pass SIGSEGV runtime: darwin/arm lldb needs to pass SIGSEGV Mar 17, 2015
@mikioh mikioh added this to the Go1.5 milestone Mar 17, 2015
crawshaw added a commit that referenced this issue Mar 23, 2015
Issue #10043 was resolved by https://golang.org/cl/7072.
This test now passes.

Change-Id: I7bdef63d9ee4edcede23613a14a2ddce14018f34
Reviewed-on: https://go-review.googlesource.com/7931
Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
@golang golang locked and limited conversation to collaborators Jun 25, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants