Skip to content

Conversation

@petrochenkov
Copy link
Contributor

cc #30095

r? @nrc

@petrochenkov petrochenkov force-pushed the owned5 branch 2 times, most recently from b225678 to e3da2a9 Compare December 19, 2015 16:22
@nrc
Copy link
Member

nrc commented Dec 20, 2015

lgtm, how did you fix the segfault?

@bors: r+

@bors
Copy link
Collaborator

bors commented Dec 20, 2015

📌 Commit e3da2a9 has been approved by nrc

@petrochenkov
Copy link
Contributor Author

how did you fix the segfault?

By not doing this (I also reduced the changes to a necessary minimum, just to be sure).

@petrochenkov
Copy link
Contributor Author

Also, rr wasn't especially more helpful than vanilla gdb, because it is a release-only segfault - it's still not clear what happens even if the error location is known, the amount of available debuginfo is vanishingly small. After spending some time trying to do assembly level debugging I gave up and spent some machine time instead by bisecting the changes and running make check.

bors added a commit that referenced this pull request Dec 20, 2015
@bors
Copy link
Collaborator

bors commented Dec 20, 2015

⌛ Testing commit e3da2a9 with merge 3d15039...

@bors bors merged commit e3da2a9 into rust-lang:master Dec 21, 2015
@petrochenkov petrochenkov deleted the owned5 branch September 21, 2016 19:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants