[#5218] Ruby Book Eng tl, ch1 question — Jon Babcock <jon@...>

13 messages 2000/10/02

[#5404] Object.foo, setters and so on — "Hal E. Fulton" <hal9000@...>

OK, here is what I think I know.

14 messages 2000/10/11

[#5425] Ruby Book Eng. tl, 9.8.11 -- seishitsu ? — Jon Babcock <jon@...>

18 messages 2000/10/11
[#5427] RE: Ruby Book Eng. tl, 9.8.11 -- seishitsu ? — OZAWA -Crouton- Sakuro <crouton@...> 2000/10/11

At Thu, 12 Oct 2000 03:49:46 +0900,

[#5429] Re: Ruby Book Eng. tl, 9.8.11 -- seishitsu ? — Jon Babcock <jon@...> 2000/10/11

Thanks for the input.

[#5432] Re: Ruby Book Eng. tl, 9.8.11 -- seishitsu ? — Yasushi Shoji <yashi@...> 2000/10/11

At Thu, 12 Oct 2000 04:53:41 +0900,

[#5516] Re: Some newbye question — ts <decoux@...>

>>>>> "D" == Davide Marchignoli <marchign@di.unipi.it> writes:

80 messages 2000/10/13
[#5531] Re: Some newbye question — matz@... (Yukihiro Matsumoto) 2000/10/14

Hi,

[#5544] Re: Some newbye question — Davide Marchignoli <marchign@...> 2000/10/15

On Sat, 14 Oct 2000, Yukihiro Matsumoto wrote:

[#5576] Re: local variables (nested, in-block, parameters, etc.) — Dave Thomas <Dave@...> 2000/10/16

matz@zetabits.com (Yukihiro Matsumoto) writes:

[#5617] Re: local variables (nested, in-block, parameters, etc.) — "Brian F. Feldman" <green@...> 2000/10/16

Dave Thomas <Dave@thomases.com> wrote:

[#5705] Dynamic languages, SWOT ? — Hugh Sasse Staff Elec Eng <hgs@...>

There has been discussion on this list/group from time to time about

16 messages 2000/10/20
[#5712] Re: Dynamic languages, SWOT ? — Charles Hixson <charleshixsn@...> 2000/10/20

Hugh Sasse Staff Elec Eng wrote:

[#5882] [RFC] Towards a new synchronisation primitive — hipster <hipster@...4all.nl>

Hello fellow rubyists,

21 messages 2000/10/26

[ruby-talk:5698] Re: Compile Problem with 1.6.1

From: nick_hynes@...
Date: 2000-10-20 04:40:11 UTC
List: ruby-talk #5698

I'd suggest you register a signal handler:

#include <signal.h>

:
:
 signal( SIGSEV, handler_func )
:
:

void handler_func( int signal_id )
{
}


Set a breakpoint in the signal handler, and then run it under KDevelop
(in debug mode)... (or some other IDE...)

#
In article <E13eW7L-0006NK-00@ev.netlab.zetabits.co.jp>,
  matz@zetabits.com (Yukihiro Matsumoto) wrote:
> Hi,
>
> In message "[ruby-talk:5168] Re: Compile Problem with 1.6.1"
>     on 00/09/28, Scott Billings <aerogemsX@netins.net> writes:
>
> |Well, an AthlonGCC bug might be the cause, but I've had no problems
> |with any other app compiled with it.
>
> Ruby is a rather complicated software.
>
> |Anyway, compiled in debugging info, all other flags the same, here's
> |the output I get from gdb:
>
> |Program received signal SIGSEGV, Segmentation fault.
> |0x400bd5fe in free () from /lib/libc.so.6
>
> This information strongly suggests that there're pointer bugs.  But I
> couldn't find any of them using checkergcc.  sigh.
>
> 							matz.
>
>


Sent via Deja.com http://www.deja.com/
Before you buy.

In This Thread

Prev Next