After upgraded to TL5, my ruby core dumped as well.
But this occurred only if the ruby was compiled by gcc. I mean, the
ruby compiled by using XL C Ver.8 did not core dumped.
The stack trace in my environment is like this:
#I omitted some dbx error…
raise.raise(??) at 0xd0313754
abort.abort() at 0xd0342cb0
rb_bug(fmt = “Segmentation fault”), line 214 in “error.c”
sigsegv(sig = 11), line 537 in “signal.c”
__modinit.find_rtinit(??, ??, ??) at 0xd032af10
__modinit.__modfini() at 0xd032afa0
cuexit.exit(??) at 0xd032005c
proc_options(argc = 0, argv = 0x2ff22c30), line 776 in “ruby.c”
ruby_process_options(argc = 2, argv = 0x2ff22c28), line 1194 in “ruby.c”
ruby_options(argc = 2, argv = 0x2ff22c28), line 1521 in “eval.c”
main(argc = 2, argv = 0x2ff22c28, envp = 0x2ff22c34), line 45 in
It seemed that my ruby core dumped after calling exit().
This might be AIX issue, I guess.
Unlike your case, I was able to compile the ruby again after upgraded
to TL5 (actually, TL5 + SP1), and it did not core dumped.
I’m using gcc 3.4.6 which I compiled using XL C, when the AIX was TL4.
Which version of gcc are you using? Where/How did you get it?
If you have XL C, it would be worth trying.
Or, contact AIX support, please.