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?