St_lookup problem with sockets on ppc

ruby-talk
1

ruby -v

  ruby 1.7.3 (2002-12-10) [powerpc-darwin6.2]

ruby -r socket -e 1

I get:

Program received signal EXC_BAD_ACCESS, Could not access memory.
st_lookup (table=0x0, key=0x487360 “SocketError”, value=0xbfffee20) at
st.c:257
257 hash_val = do_hash(key, table);
(gdb) bt
#0 st_lookup (table=0x0, key=0x487360 “SocketError”, value=0xbfffee20)
at st.c:257
#1 0x00441a98 in rb_intern (name=0x487360 “SocketError”) at
parse.y:5517
#2 0x00423858 in rb_define_class (name=0x487360 “SocketError”,
super=0) at class.c:197
#3 0x00403a98 in Init_socket () at socket.c:2392
#4 0x0001dc80 in dln_load (file=0x212e20
"/usr/local/lib/ruby/1.7/powerpc-darwin6.2/socket.bundle") at dln.c:1442
#5 0x0001110c in rb_f_require (obj=0, fname=2396416) at eval.c:5670
#6 0x0004fadc in require_libraries () at ruby.c:342
#7 0x00050920 in proc_options (argc=0, argv=0xbffffde4) at ruby.c:743
#8 0x000514b0 in ruby_process_options (argc=3, argv=0xbffffdd8) at
ruby.c:1073
#9 0x00004708 in ruby_options (argc=3, argv=0xbffffdd8) at eval.c:1208
#10 0x00002760 in main (argc=3, argv=0xbffffdd8, envp=0xbfffee20) at
main.c:49
#11 0x000024e0 in _start (argc=3, argv=0xbffffdd8, envp=0xbffffde8) at
/SourceCache/Csu/Csu-45/crt.c:267
#12 0x00002360 in start ()

Is this a port issue or a core issue?

Cheers

Dave

2

Dave Thomas wrote:

ruby -v

 ruby 1.7.3 (2002-12-10) [powerpc-darwin6.2]

ruby -r socket -e 1

I’m ok. So it’s probably a port issue…

[waisun@caspar tmp]$ ruby -v
ruby 1.7.3 (2002-12-10) [i386-linux-gnu]
[waisun@caspar tmp]$ ruby -r socket -e 1
[waisun@caspar tmp]$

···

–
Wai-Sun “Squidster” Chia
Consulting & Integration
Linux/Unix/Web Developer Dude
“Just Another Ruby Miner”

3

Hi,

ruby -v

  ruby 1.7.3 (2002-12-10) [powerpc-darwin6.2]

ruby -r socket -e 1

I get:

Program received signal EXC_BAD_ACCESS, Could not access memory.
st_lookup (table=0x0, key=0x487360 “SocketError”, value=0xbfffee20) at
st.c:257
257 hash_val = do_hash(key, table);
(gdb) bt
#0 st_lookup (table=0x0, key=0x487360 “SocketError”,
value=0xbfffee20) at st.c:257
#1 0x00441a98 in rb_intern (name=0x487360 “SocketError”) at
parse.y:5517
#2 0x00423858 in rb_define_class (name=0x487360 “SocketError”,
super=0) at class.c:197
#3 0x00403a98 in Init_socket () at socket.c:2392

st_lookup() in rb_intern() uses sym_tbl, but it must not be 0,
otherwise core classes could not be initialized.

Is this a port issue or a core issue?

I guess it’s a port issue. How did you configure ruby, and
what CFLAGS?

···

At Wed, 11 Dec 2002 15:17:25 +0900, Dave Thomas wrote:

–
Nobu Nakada

4

Ditto. Port problem most likely.

[wyzzrd@starcrusher ruby]$ ./ruby -v
ruby 1.7.3 (2002-12-10) [i586-linux]
[wyzzrd@starcrusher ruby]$ ./ruby -r socket -e 1
[wyzzrd@starcrusher ruby]$

Regards,

W. Kent Starr

···

On Wed, 2002-12-11 at 01:33, Wai-Sun Chia wrote:

Dave Thomas wrote:

ruby -v

 ruby 1.7.3 (2002-12-10) [powerpc-darwin6.2]

ruby -r socket -e 1

I’m ok. So it’s probably a port issue…

[waisun@caspar tmp]$ ruby -v
ruby 1.7.3 (2002-12-10) [i386-linux-gnu]
[waisun@caspar tmp]$ ruby -r socket -e 1
[waisun@caspar tmp]$