ruby-core

On 2/22/06, George Ogata <g_ogata@optushome.com.au> wrote:> dblack@wobblini.net writes:>> I'm still not happy about #funcall. How is one supposed to remember>> which (#send or #funcall) is which? There are a few things in Ruby>> where "you just have to memorize it" -- like the true/false arguments>> to #instance_methods, or the differences between Proc.new and lambda.>> I've always felt that these are soft spots in the language.>> #send/#funcall seems to me to be in the same category.> #funcall breaks the rules. That makes it "fun". ;-)

[#7413] Re: Module#define_method "send hack" fails with Ruby 1.9 — "Justin Bailey" <jgbailey@...> 2006/02/22

Second! I've disliked 'funcall' since I first saw it. And why break send? I

[#7419] ping.rb — "Pat Eyler" <rubypate@...>

ping.rb has bothered me for a while for two reasons. First, it really ought

4 messages 2006/02/24

[#7425] Re: ping.rb — Joel VanderWerf <vjoel@...> 2006/02/25

Pat Eyler wrote:

[#7420] Re: ping.rb — Daniel Berger <djberg96@...> 2006/02/24

--- Pat Eyler <rubypate@gmail.com> wrote:

[#7421] Re: ping.rb — "Pat Eyler" <rubypate@...> 2006/02/24

On 2/23/06, Daniel Berger <djberg96@yahoo.com> wrote:

[#7422] Syck fails with parse error on parsing multiple documents — noreply@...

Bugs item #3654, was opened at 2006-02-24 15:45

1 message 2006/02/24

[#7423] Rubygems/ri integration — Eric Hodel <drbrain@...7.net>

I just added a patch to Rubygems that allows it to generate ri data

3 messages 2006/02/24

[#7426] Re: [PATCH] Rubygems/ri integration — Ryan Davis <ryand-ruby@...> 2006/02/26

[#7479] Re: [PATCH] Rubygems/ri integration — Yukihiro Matsumoto <matz@...> 2006/03/03

Hi,

[#7424] Passing wrong data type to Win32API#call causes segfault — noreply@...

Bugs item #3658, was opened at 2006-02-24 19:33

1 message 2006/02/25

[#7434] parser bug, function call without parens across multiple lines — David Smiley <dsmiley@...>

I have encountered a counter-intuitive bug in Ruby's parser. The

5 messages 2006/02/27

[#7436] Re: parser bug, function call without parens across multiple lines — Mauricio Fernandez <mfp@...> 2006/02/27

On Tue, Feb 28, 2006 at 02:05:17AM +0900, David Smiley wrote:

[#7441] Re: parser bug, function call without parens across multiple lines — David Smiley <dsmiley@...> 2006/02/27

First of all, I'd like to apologize because my bug report was

[#7435] Re: parser bug, function call without parens across multiple lines — ts <decoux@...> 2006/02/27

>>>>> "D" == David Smiley <dsmiley@mitre.org> writes:

[#7437] Re: parser bug, function call without parens across multiple lines — Stefan Lang <langstefan@...> 2006/02/27

On Monday 27 February 2006 18:05, David Smiley wrote:

[#7438] Re: parser bug, function call without parens across multiple lines — "Yemi D. Bedu" <yemi@...>

Hello,

1 message 2006/02/27

[#7439] FYI: ruby-lang.org is on spamcop blacklists — mathew <meta@...>

dnsbl/bl.spamcop.net returned deny: for

3 messages 2006/02/27

[#7440] Re: FYI: ruby-lang.org is on spamcop blacklists — "Justin Bailey" <jgbailey@...> 2006/02/27

This is fairly serious as it breaks Google Groups/Ruby Talk list

[#7464] Re: FYI: ruby-lang.org is on spamcop blacklists — "Austin Ziegler" <halostatue@...> 2006/03/01

On 2/27/06, Justin Bailey <jgbailey@gmail.com> wrote:> This is fairly serious as it breaks Google Groups/Ruby Talk list> integration, right?

[#7442] GC Question — zdennis <zdennis@...>

I have been posting to the ruby-talk mailing list about ruby memory and GC, and I think it's ready

17 messages 2006/02/27

[#7446] Re: GC Question — "H.Yamamoto" <ocean@...2.ccsnet.ne.jp> 2006/02/28

Hello.

[#7449] Re: GC Question — "H.Yamamoto" <ocean@...2.ccsnet.ne.jp> 2006/02/28

Hello.

[#7450] Re: GC Question — "H.Yamamoto" <ocean@...2.ccsnet.ne.jp> 2006/02/28

Sorry, I lied...

[#7451] Re: GC Question — ts <decoux@...> 2006/02/28

>>>>> "H" == H Yamamoto <ocean@m2.ccsnet.ne.jp> writes:

[#7452] Re: GC Question — "H.Yamamoto" <ocean@...2.ccsnet.ne.jp> 2006/02/28

[#7453] Re: GC Question — ts <decoux@...> 2006/02/28

>>>>> "H" == H Yamamoto <ocean@m2.ccsnet.ne.jp> writes:

[#7454] Re: GC Question — "H.Yamamoto" <ocean@...2.ccsnet.ne.jp> 2006/02/28

[#7455] Re: GC Question — ts <decoux@...> 2006/02/28

>>>>> "H" == H Yamamoto <ocean@m2.ccsnet.ne.jp> writes:

[#7462] Re: GC Question — zdennis <zdennis@...> 2006/02/28

H.Yamamoto wrote:

[#7456] Re: GC Question — zdennis <zdennis@...> 2006/02/28

Attempting to apply patch to array.c from 1.8.4 I get:

[#7458] Re: GC Question — ts <decoux@...> 2006/02/28

>>>>> "z" == zdennis <zdennis@mktec.com> writes:

[#7459] Re: GC Question — zdennis <zdennis@...> 2006/02/28

ts wrote:

[#7461] Re: GC Question — ts <decoux@...> 2006/02/28

>>>>> "z" == zdennis <zdennis@mktec.com> writes:

[#7463] Re: GC Question — zdennis <zdennis@...> 2006/03/01

ts wrote:

[#7467] Re: GC Question — ts <decoux@...> 2006/03/01

>>>>> "z" == zdennis <zdennis@mktec.com> writes:

[#7457] Re: GC Question — "H.Yamamoto" <ocean@...2.ccsnet.ne.jp> 2006/02/28

Hello.

[#7460] rails segfaults at 2nd load with eval.c: No such file or directory. — noreply@...

Bugs item #3683, was opened at 2006-02-28 10:33

1 message 2006/02/28

Re: [PATCH] solaris 10 isinf and ruby_setenv fixes

From: ville.mattila@...

Date: 2006-02-01 05:30:56 UTC

List: ruby-core #7271

Hello,

Yes I experienced actual memory corruption. Here is the test run:

test_bracket(TestEnv): ./ruby/test_env.rb:19:in `[]=': failed to allocate
memory (NoMemoryError)
        from ./ruby/test_env.rb:19:in `test_bracket'
        from /install/ruby-1-8-cvs/ruby/lib/test/unit/testcase.rb:70:in
`run'
        from /install/ruby-1-8-cvs/ruby/lib/test/unit/testsuite.rb:32:in
`run'
        from /install/ruby-1-8-cvs/ruby/lib/test/unit/testsuite.rb:31:in
`run'
        from /install/ruby-1-8-cvs/ruby/lib/test/unit/testsuite.rb:32:in
`run'
        from /install/ruby-1-8-cvs/ruby/lib/test/unit/testsuite.rb:31:in
`run'
        from /install/ruby-1-8-cvs/ruby/lib/test/unit/testsuite.rb:32:in
`run'
        from /install/ruby-1-8-cvs/ruby/lib/test/unit/testsuite.rb:31:in
`run'
        from
/install/ruby-1-8-cvs/ruby/lib/test/unit/ui/testrunnermediator.rb:44:in
`run_suite'
        from
/install/ruby-1-8-cvs/ruby/lib/test/unit/ui/console/testrunner.rb:65:in
`start_mediator'
        from
/install/ruby-1-8-cvs/ruby/lib/test/unit/ui/console/testrunner.rb:39:in
`start'
        from
/install/ruby-1-8-cvs/ruby/lib/test/unit/ui/testrunnerutilities.rb:27:in
`run'
        from /install/ruby-1-8-cvs/ruby/lib/test/unit/autorunner.rb:200:in
`run'
        from /install/ruby-1-8-cvs/ruby/lib/test/unit/autorunner.rb:13:in
`run'
        from runner.rb:7


I also have run the whole test suite, otherwise this doesn't come up.
There can also be
./miniruby ../runruby.rb --extout=.ext -- -C "../test" runner.rb
--runner=console
Loaded suite .
Started
.................................................F..........................
.............................................................................
............................................................................
............................................................................
......................................................../openssl/test_ssl.rb:64:
 warning: Insecure world writable dir /install, mode 040777
../openssl/test_ssl.rb:64: warning: Insecure world writable dir /install,
mode 040777
../openssl/test_ssl.rb:64: warning: Insecure world writable dir /install,
mode 040777
../openssl/test_ssl.rb:64: warning: Insecure world writable dir /install,
mode 040777
./openssl/test_ssl.rb:64: warning: Insecure world writable dir /install,
mode 040777
./openssl/test_ssl.rb:64: warning: Insecure world writable dir /install,
mode 040777
../openssl/test_ssl.rb:64: warning: Insecure world writable dir /install,
mode 040777
../openssl/test_ssl.rb:64: warning: Insecure world writable dir /install,
mode 040777
........................................................................
...........................................................................
............................................................................................Segmentation
 Fault - core dumped
make: *** [test-all] Error 139

With the patch, everything goes smoothly.

 - Ville



|---------+--------------------------->
|         |           H.Yamamoto      |
|         |           <ocean@m2.ccsnet|
|         |           .ne.jp>         |
|         |                           |
|         |           01.02.2006 05:20|
|         |           Please respond  |
|         |           to ruby-core    |
|         |                           |
|---------+--------------------------->
  >--------------------------------------------------------------------------------------------------------------------------------------------------|
  |                                                                                                                                                  |
  |        To:      ruby-core@ruby-lang.org                                                                                                          |
  |        cc:                                                                                                                                       |
  |        Subject: Re: [PATCH]  solaris 10  isinf and ruby_setenv fixes                                                                             |
  >--------------------------------------------------------------------------------------------------------------------------------------------------|




Hello.

> 2.  ruby_setenv will cause random memory corruption. The solaris 10 man
>setnv:
>" ....
>  If the application modifies environ or the pointers to which
>     it  points,  the  behavior  of  setenv()  is  undefined. The
>     setenv() function updates the  list  of  pointers  to  which
>     environ points.
> ...
>"

You experienced actual memory corruption? Or just assumed so?

Thread

Prev Next

In This Thread

Prev Next