-
Notifications
You must be signed in to change notification settings - Fork 18k
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
Labels
Milestone
Comments
could we simply supply a stream of "continue" command to
lldb?
or make lldb do "continue" upon reception of the SIGSEGV
signal (gdb can do "catch signal SIGSEGV", and then we
can define command to be executed when SIGSEGV is
received.)
|
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 <[email protected]>
LLDB engineer says its a long standing OS X bug and recommends we work around it: |
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 <[email protected]>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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
The text was updated successfully, but these errors were encountered: