# Strange Proc#call problems with profile

**URL:** <https://www.ruby-forum.com/t/strange-proc-call-problems-with-profile/94537>\
**Category:** Ruby\
**Created:** [May 6, 2006, 6:01am UTC](https://www.ruby-forum.com/t/strange-proc-call-problems-with-profile/94537 "2006-05-06T06:01:30Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![victor123789](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/v/f0a364/32.png) [@victor123789](https://www.ruby-forum.com/u/victor123789)\
**Post date:** [May 6, 2006, 6:01am UTC](https://www.ruby-forum.com/t/strange-proc-call-problems-with-profile/94537/1 "2006-05-06T06:01:30Z")

</div>

Hello all.

I’ve striked with some strange problem.  
After transition from ruby1.8.2 =\> ruby1.9 I have the following problem:

–  
require ‘profile’

## l = lambda{|x| x} l.call([1,2,3]) #\<== error goes here

test\_profile.rb:4:in `Proc#call’: wrong argument type nil (expected  
Data)  
(TypeError)

If I comment out “require profile”, all works without errors.

What does it mean?

Thanks.

Victor.

---

<div class="post-metadata">

**Author:** ![victor123789](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/v/f0a364/32.png) [@victor123789](https://www.ruby-forum.com/u/victor123789)\
**Post date:** [May 6, 2006, 12:34pm UTC](https://www.ruby-forum.com/t/strange-proc-call-problems-with-profile/94537/2 "2006-05-06T12:34:11Z")

</div>

On Sat, May 06, 2006 at 01:01:03PM +0900, Victor S. wrote:

> (TypeError)
> 
> If I comment out “require profile”, all works without errors.

Looks like a bug in 1.9; I’m forwarding that to ruby-core:

$ cat bug2.rb  
set\_trace\_func proc{}  
l = lambda{}  
l.call  
$ ruby19 bug2.rb  
bug2.rb:3: [BUG] Segmentation fault  
ruby 1.9.0 (2006-05-01) [i686-linux]

Aborted

---

<div class="post-metadata">

**Author:** ![victor123789](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/v/f0a364/32.png) [@victor123789](https://www.ruby-forum.com/u/victor123789)\
**Post date:** [May 7, 2006, 7:49am UTC](https://www.ruby-forum.com/t/strange-proc-call-problems-with-profile/94537/3 "2006-05-07T07:49:19Z")

</div>

> > –  
> > set\_trace\_func proc{}  
> > l = lambda{}  
> > l.call  
> > $ ruby19 bug2.rb  
> > bug2.rb:3: [BUG] Segmentation fault  
> > ruby 1.9.0 (2006-05-01) [i686-linux]
> 
> Aborted

Aha. Thanks.  
Can someone advice me on temporary workaround?

> Mauricio F. - [http://eigenclass.org](http://eigenclass.org) - singular Ruby

Victor.

---

<div class="post-metadata">

**Author:** ![victor123789](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/v/f0a364/32.png) [@victor123789](https://www.ruby-forum.com/u/victor123789)\
**Post date:** [May 7, 2006, 9:10am UTC](https://www.ruby-forum.com/t/strange-proc-call-problems-with-profile/94537/4 "2006-05-07T09:10:50Z")

</div>

In message “Re: Strange Proc#call problems with profile”  
on Sun, 7 May 2006 14:47:22 +0900, “Victor S.”  
[removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) writes:

|\> Looks like a bug in 1.9; I’m forwarding that to ruby-core:

|Aha. Thanks.  
|Can someone advice me on temporary workaround?

[ruby-core:07835]

— eval.c 23 Feb 2006 04:24:39 -0000 1.890  
+++ eval.c 6 May 2006 14:41:49 -0000  
@@ -8266,3 +8243,3 @@ proc\_invoke(VALUE proc, VALUE args /\* OK  
struct BLOCK \_block;

- struct BLOCK \*data;

- struct BLOCK _data, old\_block;  
volatile VALUE result = Qundef;  
@@ -8304,2 +8277,3 @@ proc\_invoke(VALUE proc, VALUE args / OK  
/_ modify current frame \*/
- old\_block = ruby\_frame-\>block;  
ruby\_frame-\>block = &\_block;  
@@ -8316,2 +8290,3 @@ proc\_invoke(VALUE proc, VALUE args /\* OK  
POP\_TAG();
- ruby\_frame-\>block = old\_block;  
ruby\_wrapper = old\_wrapper;

---

<div class="post-metadata">

**Author:** ![victor123789](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/v/f0a364/32.png) [@victor123789](https://www.ruby-forum.com/u/victor123789)\
**Post date:** [May 7, 2006, 9:16am UTC](https://www.ruby-forum.com/t/strange-proc-call-problems-with-profile/94537/5 "2006-05-07T09:16:56Z")

</div>

> |\> Looks like a bug in 1.9; I’m forwarding that to ruby-core:
> 
> |Aha. Thanks.  
> |Can someone advice me on temporary workaround?
> 
> [ruby-core:07835]
> 
> — eval.c 23 Feb 2006 04:24:39 -0000 1.890  
> +++ eval.c 6 May 2006 14:41:49 -0000

Thanks matz! Big thanks!

Victor.