[#61822] Plan Developers Meeting Japan April 2014 — Zachary Scott <e@...>

I would like to request developers meeting around April 17 or 18 in this mo=

14 messages 2014/04/03
[#61825] Re: Plan Developers Meeting Japan April 2014 — Urabe Shyouhei <shyouhei@...> 2014/04/03

It's good if we have a meeting then.

[#61826] Re: Plan Developers Meeting Japan April 2014 — Zachary Scott <e@...> 2014/04/03

Regarding openssl issues, I=E2=80=99ve discussed possible meeting time with=

[#61833] Re: Plan Developers Meeting Japan April 2014 — Martin Bo煬et <martin.bosslet@...> 2014/04/03

Hi,

[ruby-core:62012] [ruby-trunk - Bug #9710] __builtin_setjmp/longjmp causes SEGV with mingw

From: s.wanabe@...
Date: 2014-04-13 10:54:02 UTC
List: ruby-core #62012
Issue #9710 has been updated by _ wanabe.

Backport changed from 2.0.0: UNKNOWN, 2.1: UNKNOWN to 2.0.0: REQUIRED, 2.1: REQUIRED

I guess it should be backported with #9692.

----------------------------------------
Bug #9710: __builtin_setjmp/longjmp causes SEGV with mingw
https://bugs.ruby-lang.org/issues/9710#change-46202

* Author: Hiroshi Shirosaki
* Status: Closed
* Priority: Normal
* Assignee: 
* Category: 
* Target version: 
* ruby -v: ruby 2.2.0dev (2014-04-07 trunk 45529) [x64-mingw32]
* Backport: 2.0.0: REQUIRED, 2.1: REQUIRED
----------------------------------------
Now `__builtin_setjmp/__builtin_longjmp` are used with x64-mingw.

ruby 2.2.0dev (2014-04-07 trunk 45529) [x64-mingw32]
gcc version 4.8.2 20130712 (prerelease) (Built by MinGW-builds project)


.ext/include/x64-mingw32/ruby/config.h


~~~
#define RUBY_SETJMP(env) __builtin_setjmp((env))
#define RUBY_LONGJMP(env,val) __builtin_longjmp((env),val)
~~~

But this casues SEGV with callcc.

`ruby -rcontinuation -e "callcc{|c|c.call}"`

Instead using `setjmpex/longjmp` seems to work fine.

```
#define RUBY_SETJMP(env) setjmpex((env))
#define RUBY_LONGJMP(env,val) longjmp((env),val)
```



-- 
https://bugs.ruby-lang.org/

In This Thread

Prev Next