[#7286] Re: ruby-dev summary 28206-28273 — ara.t.howard@...

On Thu, 2 Feb 2006, Minero Aoki wrote:

23 messages 2006/02/02
[#7292] ANDCALL / iff? / &? (was Re: ruby-dev summary 28206-28273) — mathew <meta@...> 2006/02/02

[#7293] Re: ANDCALL / iff? / &? (was Re: ruby-dev summary 28206-28273) — mathew <meta@...> 2006/02/02

mathew wrote:

[#7298] Re: ANDCALL / iff? / &? (was Re: ruby-dev summary 28206-28273) — James Britt <ruby@...> 2006/02/03

mathew wrote:

[#7310] Re: ANDCALL / iff? / &? (was Re: ruby-dev summary 28206-28273) — Evan Webb <evanwebb@...> 2006/02/07

I'm not sure we even need the 'with' syntax. Even if we do, it breaks

[#7311] Re: ANDCALL / iff? / &? (was Re: ruby-dev summary 28206-28273) — Eero Saynatkari <ruby-ml@...> 2006/02/07

On 2006.02.07 10:03, Evan Webb wrote:

[#7313] Re: ANDCALL / iff? / &? (was Re: ruby-dev summary 28206-28273) — Evan Webb <evanwebb@...> 2006/02/07

Umm, on what version are you seeing a warning there? I don't and never

[#7315] Re: ANDCALL / iff? / &? (was Re: ruby-dev summary 28206-28273) — Eero Saynatkari <ruby-ml@...> 2006/02/07

On 2006.02.07 14:47, Evan Webb wrote:

[#7316] Re: ANDCALL / iff? / &? (was Re: ruby-dev summary 28206-28273) — Evan Webb <evanwebb@...> 2006/02/07

I'd by far prefer it never emit a warning. The warning is assumes you

[#7305] Re: Problem with weak references on OS X 10.3 — Mauricio Fernandez <mfp@...>

On Sun, Feb 05, 2006 at 08:33:40PM +0900, Christian Neukirchen wrote:

28 messages 2006/02/05
[#7401] Symbols overlap ordinary objects, especially on OS X (Was: Re: Problem with weak references on OS X 10.3) — Eric Hodel <drbrain@...7.net> 2006/02/22

On Feb 5, 2006, at 5:05 AM, Mauricio Fernandez wrote:

[#7414] Re: Symbols overlap ordinary objects, especially on OS X (Was: Re: Problem with weak references on OS X 10.3) — Mauricio Fernandez <mfp@...> 2006/02/23

On Wed, Feb 22, 2006 at 02:21:24PM +0900, Eric Hodel wrote:

[#7428] Re: Symbols overlap ordinary objects, especially on OS X (Was: Re: Problem with weak references on OS X 10.3) — Tanaka Akira <akr@...17n.org> 2006/02/26

In article <1140968746.321377.18843.nullmailer@x31.priv.netlab.jp>,

[#7444] Re: Symbols overlap ordinary objects, especially on OS X (Was: Re: Problem with weak references on OS X 10.3) — nobu@... 2006/02/28

Hi,

[#7445] Re: Symbols overlap ordinary objects, especially on OS X (Was: Re: Problem with weak references on OS X 10.3) — Tanaka Akira <akr@...17n.org> 2006/02/28

In article <m1FDshr-0006MNC@Knoppix>,

[#7447] Re: Symbols overlap ordinary objects, especially on OS X (Was: Re: Problem with weak references on OS X 10.3) — Tanaka Akira <akr@...17n.org> 2006/02/28

In article <87irr047sx.fsf@m17n.org>,

[#7448] Re: Symbols overlap ordinary objects, especially on OS X (Was: Re: Problem with weak references on OS X 10.3) — Tanaka Akira <akr@...17n.org> 2006/02/28

In article <87vev0hxu5.fsf@m17n.org>,

[#7465] Re: Symbols overlap ordinary objects, especially on OS X (Was: Re: Problem with weak references on OS X 10.3) — "Evan Webb" <evanwebb@...> 2006/03/01

Just my quick 2 cents...

[#7468] Re: Symbols overlap ordinary objects, especially on OS X (Was: Re: Problem with weak references on OS X 10.3) — Tanaka Akira <akr@...17n.org> 2006/03/01

In article <92f5f81d0602281855g27e78f4eua8bf20e0b8e47b68@mail.gmail.com>,

[#7403] Module#define_method "send hack" fails with Ruby 1.9 — Emiel van de Laar <emiel@...>

Hi List,

12 messages 2006/02/22
[#7404] Re: Module#define_method "send hack" fails with Ruby 1.9 — George Ogata <g_ogata@...> 2006/02/22

Emiel van de Laar <emiel@rednode.nl> writes:

[#7406] Re: Module#define_method "send hack" fails with Ruby 1.9 — dblack@... 2006/02/22

Hi --

[#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

Ruby 1.8 CVS miniruby core dumps

From: ville.mattila@...
Date: 2006-02-15 07:53:51 UTC
List: ruby-core #7367
Hello,

On
uname -a
SunOS future-beat 5.10 Generic_118844-28 i86pc i386 i86pc

current cvs dumps. The dumps appeared with changes on date
cvs update -rruby_1_8 -D'Tue Feb 14 13:07:02 2006 UTC'.
This happens both 32 and 64 bit versions.


Here is some debug data:

cc -g -mt -fsimple=1 -xbuiltin=%all -xlibmil -xlibmopt -xtarget=opteron
-xarch=amd64  -DRUBY_EXPORT  -I. -I..  -c ../dmyext.c
cc: Warning: -fsimple option is ignored.
ar rcu libruby-static.a array.o bignum.o class.o compar.o dir.o dln.o
enum.o error.o eval.o file.o gc.o hash.o inits.o io.o marshal.o math.o
numeric.o object.o pack.o parse.o process.o prec.o random.o range.o re.o
regex.o ruby.o signal.o sprintf.o st.o string.o struct.o time.o util.o
variable.o version.o flock.o  dmyext.o
cc -g -mt -fsimple=1 -xbuiltin=%all -xlibmil -xlibmopt -xtarget=opteron
-xarch=amd64  -DRUBY_EXPORT  -I. -I..  -c ../main.c
cc: Warning: -fsimple option is ignored.
cc main.o  libruby-static.a -ldl -lm   -o miniruby -g -mt -fsimple=1
-xbuiltin=%all -xlibmil -xlibmopt -xtarget=opteron -xarch=amd64
-DRUBY_EXPORT  -xtarget=opteron -xarch=amd64
cc: Warning: -fsimple option is ignored.
../lib/fileutils.rb:963: [BUG] Segmentation fault
ruby 1.8.4 (2006-02-14) [i386-solaris2.10]

make: *** [.rbconfig.time] Abort (core dumped)
bash-3.00# dbx miniruby core
For information about new features see `help changes'
To remove this message, put `dbxenv suppress_startup_message 7.5' in your
.dbxrc
Reading miniruby
core file header read successfully
Reading ld.so.1
Reading libdl.so.1
Reading libm.so.2
Reading libthread.so.1
Reading libc.so.1
t@null (l@1) program terminated by signal ABRT (Abort)
0xfffffd7fff2cde5a: __lwp_kill+0x000a:  jae      __lwp_kill+0x18        [
0xfffffd7fff2cde68, .+0xe ]
Current function is rb_bug
  214       abort();
(dbx) bt
bt: not found
(dbx) where
  [1] __lwp_kill(0x1, 0x6, 0xffffffff861d0040, 0xfffffd7fff2ce74e,
0xfffffd7fff2e3640, 0xfffffd7fffdfbef0), at 0xfffffd7fff2cde5a
  [2] _thr_kill(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0xfffffd7fff2c8e83
  [3] raise(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0xfffffd7fff2773e9
  [4] abort(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0xfffffd7fff25a3d0
=>[5] rb_bug(fmt = 0x58be60 "Segmentation fault", ... = 0x500f3c, ...),
line 214 in "error.c"
  [6] sigsegv(sig = 11), line 447 in "signal.c"
  [7] __sighndlr(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0xfffffd7fff2cad86
  [8] call_user_handler(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at
0xfffffd7fff2c0192
  [9] sigacthandler(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0xfffffd7fff2c0378
  ---- called from signal handler with signal 11 (SIGSEGV) ------
  [10] strlen(0x0, 0x0, 0xfffffd7fffdfd2f8, 0x73, 0x0, 0x0), at
0xfffffd7fff24e000
  [11] _ndoprnt(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0xfffffd7fff2a541a
  [12] snprintf(0x0, 0x0, 0x0, 0x0, 0x0, 0x0), at 0xfffffd7fff2a65a5
  [13] backtrace(lev = -1), line 6207 in "eval.c"
  [14] make_backtrace(), line 6275 in "eval.c"
  [15] rb_longjmp(tag = 6, mesg = 7812144U), line 4522 in "eval.c"
  [16] rb_exc_raise(mesg = 7812144U), line 4571 in "eval.c"
  [17] rb_raise(exc = 6401720U, fmt = 0x584050 "no such file to load --
%s", ... = 0xfffffd7fffdfde70, ...), line 1061 in "error.c"
  [18] load_failed(fname = 6087880U), line 7052 in "eval.c"
  [19] rb_require_safe(fname = 6087880U, safe = 0), line 7133 in "eval.c"
  [20] rb_f_require(obj = 7822344U, fname = 7812384U), line 6986 in
"eval.c"
  [21] call_cfunc(func = 0x46bae0 = &rb_f_require(VALUE obj, VALUE fname),
recv = 7822344U, len = 1, argc = 1, argv = 0xfffffd7fffdfe2d0), line 5611
in "eval.c"
  [22] rb_call0(klass = 6432120U, recv = 7822344U, id = 9505U, oid = 9505U,
argc = 1, argv = 0xfffffd7fffdfe2d0, body = 0x603d08, flags = 2), line 5756
in "eval.c"
  [23] rb_call(klass = 6432120U, recv = 7822344U, mid = 9505U, argc = 1,
argv = 0xfffffd7fffdfe2d0, scope = 1), line 5990 in "eval.c"
  [24] rb_eval(self = 7822344U, n = 0x5cdd48), line 3444 in "eval.c"
  [25] rb_eval(self = 7822344U, n = 0x5f6950), line 3244 in "eval.c"
  [26] module_setup(module = 7822344U, n = 0x775c58), line 4136 in "eval.c"
  [27] rb_eval(self = 6422320U, n = 0x775c30), line 4044 in "eval.c"
  [28] eval_node(self = 6422320U, node = 0x775c30), line 1415 in "eval.c"
  [29] rb_load(fname = 6257640U, wrap = 0), line 6783 in "eval.c"
  [30] rb_require_safe(fname = 6293760U, safe = 0), line 7103 in "eval.c"
  [31] rb_f_require(obj = 6422320U, fname = 6258000U), line 6986 in
"eval.c"
  [32] call_cfunc(func = 0x46bae0 = &rb_f_require(VALUE obj, VALUE fname),
recv = 6422320U, len = 1, argc = 1, argv = 0xfffffd7fffdff4a0), line 5611
in "eval.c"
  [33] rb_call0(klass = 6432120U, recv = 6422320U, id = 9505U, oid = 9505U,
argc = 1, argv = 0xfffffd7fffdff4a0, body = 0x603d08, flags = 2), line 5756
in "eval.c"
  [34] rb_call(klass = 6432120U, recv = 6422320U, mid = 9505U, argc = 1,
argv = 0xfffffd7fffdff4a0, scope = 1), line 5990 in "eval.c"
  [35] rb_eval(self = 6422320U, n = 0x600db0), line 3444 in "eval.c"
  [36] eval_node(self = 6422320U, node = 0x600db0), line 1415 in "eval.c"
  [37] ruby_exec_internal(), line 1590 in "eval.c"
  [38] ruby_exec(), line 1610 in "eval.c"
  [39] ruby_run(), line 1620 in "eval.c"
  [40] main(argc = 6, argv = 0xfffffd7fffdff848, envp =
0xfffffd7fffdff880), line 46 in "main.c"
(dbx)




In This Thread

Prev Next