Andrew Hunt <Andy / Toolshed.Com> writes:

> When I point the browser to a .rb script, all I get in the error log
> is: 
> 
> ruby: [BUG] Segmentation fault

I get sort of the same result. I tried it on Apache 1.3.9, mod_ruby
0.1.7.

If I run any script that tries to do output, I get

   [Wed May 17 23:21:24 2000] [notice] child pid 28749 exit signal
   Segmentation fault (11)

in the error log.

Running strace -f on httpd shows mod_ruby attempting to write (in this 
case an error message, as the script contains a 'raise' statement)

[pid 28953] read(4, "raise \"hell\"\n", 4096) = 13
[pid 28953] gettimeofday({958625232, 962631}, NULL) = 0
[pid 28953] select(1, [0], [], [], {298, 997164}) = 1 (in [0], left {299, 0})
[pid 28953] read(4, "", 4096)           = 0
[pid 28953] close(4)                    = 0
[pid 28953] munmap(0x400b5000, 4096)    = 0
[pid 28953] rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
[pid 28953] time(NULL)                  = 958625232
[pid 28953] write(15, "[Wed May 17 23:47:12 2000] [erro"..., 104) = 104
[pid 28953] --- SIGSEGV (Segmentation fault) ---


However, if I create a script containing just a single break
statement, I get

   ruby:0: unexpected break

reported in my browser window.


Just more info.


Dave