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

ruby 2.5.1 #2

Closed
wants to merge 1 commit into
base: master
from

Conversation

Projects
None yet
3 participants
@fd00
Copy link

fd00 commented Jun 2, 2018

try to package ruby 2.5.1

  • update fedora url
  • add new fedora patches
  • remove unapplicable patches

logs : https://gist.github.com/fd00/9273434babe316334e18ea1649c2baca

@yselkowitz

This comment has been minimized.

Copy link
Contributor

yselkowitz commented Jun 4, 2018

I have been working on 2.5.1, which I just pushed to git for the sake of this discussion. Unfortunately, I have been getting SEGVs in rdoc on 32-bit only which have prevented me from completing the upgrade, and I haven't had time to debug it. Did you try on 32-bit?

@fd00

This comment has been minimized.

Copy link
Author

fd00 commented Jun 4, 2018

I have been working on 2.5.1, which I just pushed to git for the sake of this discussion.

Thanks!

Did you try on 32-bit?

Not yet. But I'll try it.

@fd00

This comment has been minimized.

Copy link
Author

fd00 commented Jun 4, 2018

@yselkowitz
Can you tell me how to prepare i686-pc-cygwin building environment on x86_64-cygwin if possible?

@yselkowitz

This comment has been minimized.

Copy link
Contributor

yselkowitz commented Jun 4, 2018

Simply install 32-bit cygwin with the 32-bit installer in a separate directory from your 64-bit installation. They can peacefully coexist side-by-side.

@fd00

This comment has been minimized.

Copy link
Author

fd00 commented Jun 4, 2018

I reproduce SEGV in rdoc on 32-bit.

But gdb couldn't catch it.

It seems that ruby's internal handler catches SEGV.

Do you know how to catch SEGV?

@yselkowitz

This comment has been minimized.

Copy link
Contributor

yselkowitz commented Jun 6, 2018

Sorry, never had to debug ruby before. Does strace give anything useful?

@yselkowitz

This comment has been minimized.

Copy link
Contributor

yselkowitz commented Jun 17, 2018

Would https://bugs.ruby-lang.org/issues/13999 be related somehow?

@fd00

This comment has been minimized.

Copy link
Author

fd00 commented Jun 19, 2018

Assignee (hsbt) said that he has not been able to confirm the issue. (I met him directly.)

@jon-turney

This comment has been minimized.

Copy link
Member

jon-turney commented Jun 28, 2018

Do you know how to catch SEGV?

gdb should get a chance to handle the SEGV before the signal handler is run.

Possibly you need 'set cygwin-exceptions on'

See https://cygwin.com/faq.html#faq.programming.debugging-cygwin

@cup cup referenced this pull request Jun 28, 2018

Closed

Request new Ruby release #1

@fd00

This comment has been minimized.

Copy link
Author

fd00 commented Jul 3, 2018

I couldn't handle SIGSEGV though 'set cygwin-exception on'
(signal handler seems to be run)

@fd00

This comment has been minimized.

Copy link
Author

fd00 commented Dec 25, 2018

Unfortunately, I have been getting SEGVs in rdoc on 32-bit only

This problem seems resolved in 2.6. Please try it.

@fd00

This comment has been minimized.

Copy link
Author

fd00 commented Jan 10, 2019

I will submit a new pull request (for ruby 2.6.0), so I will close this PR.

@fd00 fd00 closed this Jan 10, 2019

This was referenced Feb 16, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment