From: Ralph Shnelvar <ralphs@...32.com>
Date: 2010-09-28T04:02:22+09:00
Subject: Re: Segmentation Fault; more info?

------------127364C266A8587
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit

Chuck,



Monday, September 27, 2010, 12:44:14 PM, you wrote:


CR> On Sep 27, 2010, at 1:04 PM, Ralph Shnelvar wrote:

>> Luis,



>> Monday, September 27, 2010, 9:55:13 AM, you wrote:

>> LL> On Sep 27, 12:48 pm, Ralph Shnelvar <ral...@dos32.com> wrote:
>>>> [Note:  parts of this message were removed to make it a legal post.]

>>>> I am getting a segmentation fault.

>>>> Is there some way to get more information about what caused the fault?

>> LL> Along the segmentation fault you should be seen the backtrace of it.

>> LL> --
>> LL> Luis Lavena

>> I wish I did.

CR> You haven't provided any useful information for us to help you (platform, ruby version, code example that causes the crash, etc), but I'm going to try again anyway.

CR> If you are running on a UNIX platform with gdb installed, try this:

CR> gdb --args ruby <script name>

CR> When gdb starts up, type "run" at the prompt. When it crashes this time you might be able to get more information as to location (type 'bt' to get a backtrace from gdb).

CR> cr

Sorry ... Windows Platform.
[BUG] Segmentation fault
ruby 1.8.7 (2010-01-10 patchlevel 249) [i386-mingw32]

The program is an FXRuby program with about 4 threads running.  Trimming the problem down is not an option.

I was hoping there was some cross-platform general way of getting that info.
------------127364C266A8587--