maintainer-feedback requested: [Bug 206108] lang/ruby21: fix setjmp clobbered variables (using clang 3.8.0 and optimizing for 'high' CPUs)
Dimitry Andric has reassigned Bugzilla Automation 's request for maintainer-feedback to r...@freebsd.org: Bug 206108: lang/ruby21: fix setjmp clobbered variables (using clang 3.8.0 and optimizing for 'high' CPUs) https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206108 --- Description --- Created attachment 165369 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=165369&action=edit Mark several variables volatile so they won't have undefined state after setjmp() During my preparations for bug 206074 (exp-run for clang 3.8.0), I noticed that lang/ruby21 would sometimes crash during the build. Specifically, on i386, with CPUTYPE=ivybridge, you would get segfaults in miniruby. It turns out these are because there are several places in ruby where setjmp() is used, and where not all variables accessed after setjmp() are marked volatile. This can cause them to have undefined state. Fix this by marking several variables in different functions volatile. These patches were obtained from NetBSD pkgsrc, thanks to Jörg Sonnenberger for the hint. ___ freebsd-ruby@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ruby To unsubscribe, send any mail to "freebsd-ruby-unsubscr...@freebsd.org"
[Bug 206108] lang/ruby21: fix setjmp clobbered variables (using clang 3.8.0 and optimizing for 'high' CPUs)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206108 Bug ID: 206108 Summary: lang/ruby21: fix setjmp clobbered variables (using clang 3.8.0 and optimizing for 'high' CPUs) Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: Individual Port(s) Assignee: r...@freebsd.org Reporter: d...@freebsd.org Flags: maintainer-feedback?(r...@freebsd.org) Assignee: r...@freebsd.org Created attachment 165369 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=165369&action=edit Mark several variables volatile so they won't have undefined state after setjmp() During my preparations for bug 206074 (exp-run for clang 3.8.0), I noticed that lang/ruby21 would sometimes crash during the build. Specifically, on i386, with CPUTYPE=ivybridge, you would get segfaults in miniruby. It turns out these are because there are several places in ruby where setjmp() is used, and where not all variables accessed after setjmp() are marked volatile. This can cause them to have undefined state. Fix this by marking several variables in different functions volatile. These patches were obtained from NetBSD pkgsrc, thanks to Jörg Sonnenberger for the hint. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-ruby@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ruby To unsubscribe, send any mail to "freebsd-ruby-unsubscr...@freebsd.org"
maintainer-feedback requested: [Bug 206111] lang/ruby23: fix setjmp clobbered variables (using clang 3.8.0 and optimizing for 'high' CPUs)
Dimitry Andric has reassigned Bugzilla Automation 's request for maintainer-feedback to r...@freebsd.org: Bug 206111: lang/ruby23: fix setjmp clobbered variables (using clang 3.8.0 and optimizing for 'high' CPUs) https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206111 --- Description --- Created attachment 165371 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=165371&action=edit Mark several variables volatile so they won't have undefined state after setjmp() During my preparations for bug 206074 (exp-run for clang 3.8.0), I noticed that lang/ruby23 would sometimes crash during the build. Specifically, on i386, with CPUTYPE=ivybridge, you would get segfaults in miniruby. It turns out these are because there are several places in ruby where setjmp() is used, and where not all variables accessed after setjmp() are marked volatile. This can cause them to have undefined state. Fix this by marking several variables in different functions volatile. These patches were obtained from NetBSD pkgsrc, thanks to Jörg Sonnenberger for the hint. ___ freebsd-ruby@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ruby To unsubscribe, send any mail to "freebsd-ruby-unsubscr...@freebsd.org"
[Bug 206108] lang/ruby21: fix setjmp clobbered variables (using clang 3.8.0 and optimizing for 'high' CPUs)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206108 Kubilay Kocak changed: What|Removed |Added See Also||https://bugs.freebsd.org/bu ||gzilla/show_bug.cgi?id=2060 ||74 Flags||merge-quarterly? Keywords||needs-qa, patch --- Comment #1 from Kubilay Kocak --- Thanks Dimitry :) Should these also go upstream? Are later versions of ruby likely to be affected? -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-ruby@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ruby To unsubscribe, send any mail to "freebsd-ruby-unsubscr...@freebsd.org"
[Bug 206111] lang/ruby23: fix setjmp clobbered variables (using clang 3.8.0 and optimizing for 'high' CPUs)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206111 Bug ID: 206111 Summary: lang/ruby23: fix setjmp clobbered variables (using clang 3.8.0 and optimizing for 'high' CPUs) Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: Individual Port(s) Assignee: r...@freebsd.org Reporter: d...@freebsd.org Assignee: r...@freebsd.org Flags: maintainer-feedback?(r...@freebsd.org) Created attachment 165371 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=165371&action=edit Mark several variables volatile so they won't have undefined state after setjmp() During my preparations for bug 206074 (exp-run for clang 3.8.0), I noticed that lang/ruby23 would sometimes crash during the build. Specifically, on i386, with CPUTYPE=ivybridge, you would get segfaults in miniruby. It turns out these are because there are several places in ruby where setjmp() is used, and where not all variables accessed after setjmp() are marked volatile. This can cause them to have undefined state. Fix this by marking several variables in different functions volatile. These patches were obtained from NetBSD pkgsrc, thanks to Jörg Sonnenberger for the hint. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-ruby@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ruby To unsubscribe, send any mail to "freebsd-ruby-unsubscr...@freebsd.org"
[Bug 206110] lang/ruby22: fix setjmp clobbered variables (using clang 3.8.0 and optimizing for 'high' CPUs)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206110 Bug ID: 206110 Summary: lang/ruby22: fix setjmp clobbered variables (using clang 3.8.0 and optimizing for 'high' CPUs) Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: Individual Port(s) Assignee: r...@freebsd.org Reporter: d...@freebsd.org Flags: maintainer-feedback?(r...@freebsd.org) Assignee: r...@freebsd.org Created attachment 165370 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=165370&action=edit Mark several variables volatile so they won't have undefined state after setjmp() During my preparations for bug 206074 (exp-run for clang 3.8.0), I noticed that lang/ruby22 would sometimes crash during the build. Specifically, on i386, with CPUTYPE=ivybridge, you would get segfaults in miniruby. It turns out these are because there are several places in ruby where setjmp() is used, and where not all variables accessed after setjmp() are marked volatile. This can cause them to have undefined state. Fix this by marking several variables in different functions volatile. These patches were obtained from NetBSD pkgsrc, thanks to Jörg Sonnenberger for the hint. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-ruby@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ruby To unsubscribe, send any mail to "freebsd-ruby-unsubscr...@freebsd.org"
maintainer-feedback requested: [Bug 206110] lang/ruby22: fix setjmp clobbered variables (using clang 3.8.0 and optimizing for 'high' CPUs)
Dimitry Andric has reassigned Bugzilla Automation 's request for maintainer-feedback to r...@freebsd.org: Bug 206110: lang/ruby22: fix setjmp clobbered variables (using clang 3.8.0 and optimizing for 'high' CPUs) https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206110 --- Description --- Created attachment 165370 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=165370&action=edit Mark several variables volatile so they won't have undefined state after setjmp() During my preparations for bug 206074 (exp-run for clang 3.8.0), I noticed that lang/ruby22 would sometimes crash during the build. Specifically, on i386, with CPUTYPE=ivybridge, you would get segfaults in miniruby. It turns out these are because there are several places in ruby where setjmp() is used, and where not all variables accessed after setjmp() are marked volatile. This can cause them to have undefined state. Fix this by marking several variables in different functions volatile. These patches were obtained from NetBSD pkgsrc, thanks to Jörg Sonnenberger for the hint. ___ freebsd-ruby@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ruby To unsubscribe, send any mail to "freebsd-ruby-unsubscr...@freebsd.org"
[Bug 206108] lang/ruby21: fix setjmp clobbered variables (using clang 3.8.0 and optimizing for 'high' CPUs)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206108 Kubilay Kocak changed: What|Removed |Added See Also|https://bugs.freebsd.org/bu | |gzilla/show_bug.cgi?id=2060 | |74 | Blocks||206074 Referenced Bugs: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206074 [Bug 206074] [exp-run] Update clang in base to 3.8.0-r256945 (snapshot) -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-ruby@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ruby To unsubscribe, send any mail to "freebsd-ruby-unsubscr...@freebsd.org"
[Bug 206111] lang/ruby23: fix setjmp clobbered variables (using clang 3.8.0 and optimizing for 'high' CPUs)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206111 Kubilay Kocak changed: What|Removed |Added Blocks||206074 Flags||merge-quarterly? Keywords||needs-qa, patch Referenced Bugs: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206074 [Bug 206074] [exp-run] Update clang in base to 3.8.0-r256945 (snapshot) -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-ruby@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ruby To unsubscribe, send any mail to "freebsd-ruby-unsubscr...@freebsd.org"
[Bug 206108] lang/ruby21: fix setjmp clobbered variables (using clang 3.8.0 and optimizing for 'high' CPUs)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206108 --- Comment #2 from Dimitry Andric --- (In reply to Kubilay Kocak from comment #1) > Should these also go upstream? If upstream will accept them, yes please. :) > Are later versions of ruby likely to be affected? Yes, I submitted bug 206110 for lang/ruby22 and bug 206111 for lang/ruby23. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-ruby@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ruby To unsubscribe, send any mail to "freebsd-ruby-unsubscr...@freebsd.org"
[Bug 206110] lang/ruby22: fix setjmp clobbered variables (using clang 3.8.0 and optimizing for 'high' CPUs)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206110 Kubilay Kocak changed: What|Removed |Added Blocks||206074 Referenced Bugs: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206074 [Bug 206074] [exp-run] Update clang in base to 3.8.0-r256945 (snapshot) -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-ruby@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ruby To unsubscribe, send any mail to "freebsd-ruby-unsubscr...@freebsd.org"
[Bug 206108] lang/ruby21: fix setjmp clobbered variables (using clang 3.8.0 and optimizing for 'high' CPUs)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206108 --- Comment #3 from Dimitry Andric --- Also note that during the exp-run for bug 206074, problems are not likely to show up, since the i386 arch still defaults to the i486 CPU. But these fixes are nice to have anyway. -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-ruby@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ruby To unsubscribe, send any mail to "freebsd-ruby-unsubscr...@freebsd.org"
[Bug 206111] lang/ruby23: fix setjmp clobbered variables (using clang 3.8.0 and optimizing for 'high' CPUs)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206111 Kubilay Kocak changed: What|Removed |Added Blocks|206074 | See Also||https://bugs.freebsd.org/bu ||gzilla/show_bug.cgi?id=2060 ||74 Referenced Bugs: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206074 [Bug 206074] [exp-run] Update clang in base to 3.8.0-r256945 (snapshot) -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-ruby@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ruby To unsubscribe, send any mail to "freebsd-ruby-unsubscr...@freebsd.org"
[Bug 206110] lang/ruby22: fix setjmp clobbered variables (using clang 3.8.0 and optimizing for 'high' CPUs)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206110 Kubilay Kocak changed: What|Removed |Added Blocks|206074 | See Also||https://bugs.freebsd.org/bu ||gzilla/show_bug.cgi?id=2060 ||74 Referenced Bugs: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206074 [Bug 206074] [exp-run] Update clang in base to 3.8.0-r256945 (snapshot) -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-ruby@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ruby To unsubscribe, send any mail to "freebsd-ruby-unsubscr...@freebsd.org"
[Bug 206108] lang/ruby21: fix setjmp clobbered variables (using clang 3.8.0 and optimizing for 'high' CPUs)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206108 Kubilay Kocak changed: What|Removed |Added Blocks|206074 | See Also||https://bugs.freebsd.org/bu ||gzilla/show_bug.cgi?id=2060 ||74 Referenced Bugs: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206074 [Bug 206074] [exp-run] Update clang in base to 3.8.0-r256945 (snapshot) -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-ruby@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ruby To unsubscribe, send any mail to "freebsd-ruby-unsubscr...@freebsd.org"
[Bug 206113] databases/rubygem-state_machines-activerecord: fix wrong dependency (and make port usable again)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206113 Torsten Zühlsdorff changed: What|Removed |Added CC||r...@freebsd.org Attachment #165375||maintainer-approval?(ruby@F Flags||reeBSD.org) -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-ruby@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ruby To unsubscribe, send any mail to "freebsd-ruby-unsubscr...@freebsd.org"
maintainer-approval requested: [Bug 206113] databases/rubygem-state_machines-activerecord: fix wrong dependency (and make port usable again) : [Attachment 165375] patch to fix dependency
Torsten Zühlsdorff has asked r...@freebsd.org for maintainer-approval: Bug 206113: databases/rubygem-state_machines-activerecord: fix wrong dependency (and make port usable again) https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206113 Attachment 165375: patch to fix dependency https://bugs.freebsd.org/bugzilla/attachment.cgi?id=165375&action=edit ___ freebsd-ruby@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ruby To unsubscribe, send any mail to "freebsd-ruby-unsubscr...@freebsd.org"
[Bug 206113] databases/rubygem-state_machines-activerecord: fix wrong dependency (and make port usable again)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206113 Torsten Zühlsdorff changed: What|Removed |Added Blocks||202468 Referenced Bugs: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=202468 [Bug 202468] [new port] www/gitlab -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-ruby@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ruby To unsubscribe, send any mail to "freebsd-ruby-unsubscr...@freebsd.org"
[Bug 206113] databases/rubygem-state_machines-activerecord: fix wrong dependency (and make port usable again)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206113 Torsten Zühlsdorff changed: What|Removed |Added CC||sunp...@freebsd.org Attachment #165375|maintainer-approval?(ruby@F |maintainer-approval?(sunpoe Flags|reeBSD.org) |t...@freebsd.org) -- You are receiving this mail because: You are on the CC list for the bug. ___ freebsd-ruby@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ruby To unsubscribe, send any mail to "freebsd-ruby-unsubscr...@freebsd.org"
Problem reports for r...@freebsd.org that need special attention
To view an individual PR, use: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=(Bug Id). The following is a listing of current problems submitted by FreeBSD users, which need special attention. These represent problem reports covering all versions including experimental development code and obsolete releases. Status |Bug Id | Description +---+--- In Progress |199141 | lang/ruby22: [PATCH][feature request] completely 1 problems total for which you should take action. ___ freebsd-ruby@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ruby To unsubscribe, send any mail to "freebsd-ruby-unsubscr...@freebsd.org"
Application Authentication
Hello.I was in the BSD website reading info, because I have an application that when I launch it it brings me back an error 5.5.1 that requires authentication. Now that has nothing to do with my email service, cause I have no issues whatsoever with it,I tried all kinds of settings within my router and authentication requirements, with no results.I am self taught in most areas with good results, but I am stuck and I feel that I am in need of a higher knowledge-base, that is why I am sending you this email.The app is about bitcoinsthat I am not successful into completing. Goes through all the steps until the final that needs to connect to the server, thus giving me the famous 5.5.1.Thanks in advance with any info and suggestions.Toli ___ freebsd-ruby@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ruby To unsubscribe, send any mail to "freebsd-ruby-unsubscr...@freebsd.org"
