Advertisements

On Mon, 19 Jan 2004 wrote:
>Hi,
>
>At Mon, 19 Jan 2004 06:51:04 +0900,
>Ferenc Engard wrote:
>> This is a P4 celeron 2100MHz machine. On my home machine, which is a
>> P233, which is a also a 1.8.1 (2003-11-11), the crash never occurs.
>
>Sounds like concerning to pthread support. Try with CVS HEAD
>version. And can't you get stack trace from core?

I have tried on another debian with the actual ruby package
(2003-12-27), and it didn't segfaulted. So it is possible that the
problem is not with ruby.

How can I core dump? Right now, I am not at the machine, so apologize
if it dumps core automatically.

If it is possible, I wouldn't try the CVS version, as I have a real
tight deadline to deliver my program (hence this new distro-related
problem).

I guess my glibc (pthreads) version is 2.3.2.

It is a real big problem to me, if I cannot install my script to these
mdk boxes... ((

wrote:
>
> Hi,
>
> At Tue, 20 Jan 2004 07:42:41 +0900,
> Ferenc Engard wrote:
> > I still cannot know how to dump core, but running 3 times from gdb
> > caused 3 segfaults in different places.
>
> Try "ulimit -c unlimited" to make core.
>
> > Here are the backtraces (sorry about the long mail):
>
> All seem related with GC. I guess it might be fixed in CVS
> HEAD, or disapper by configuring with --disable-pthread.

Does it affect multithreading (i.e., tk)?

Anyway, it seems that the problem exists only on mandrake, even with
newer ruby than on my debian box. The latest one was tried is
2003-12-27, and on debian I was happy with 2003-11-11. Are you sure
compiling the HEAD version solves the problem?

Guest

At Tue, 20 Jan 2004 15:14:49 +0900,
Ferenc Engard wrote:
> > > Here are the backtraces (sorry about the long mail):
> >
> > All seem related with GC. I guess it might be fixed in CVS
> > HEAD, or disapper by configuring with --disable-pthread.
>
> Does it affect multithreading (i.e., tk)?

It should have worked before --enable-pthread was introduced.
> Anyway, it seems that the problem exists only on mandrake, even with
> newer ruby than on my debian box. The latest one was tried is
> 2003-12-27, and on debian I was happy with 2003-11-11. Are you sure
> compiling the HEAD version solves the problem?

Though I'm not sure, there are some fixes which are not
backported to 1.8 yet.

On Tue, 20 Jan 2004 wrote:
>Hi,
>
>At Tue, 20 Jan 2004 15:14:49 +0900,
>Ferenc Engard wrote:
>> > > Here are the backtraces (sorry about the long mail):
>> >
>> > All seem related with GC. I guess it might be fixed in CVS
>> > HEAD, or disapper by configuring with --disable-pthread.
>>
>> Does it affect multithreading (i.e., tk)?
>
>It should have worked before --enable-pthread was introduced.
>
>> Anyway, it seems that the problem exists only on mandrake, even with
>> newer ruby than on my debian box. The latest one was tried is
>> 2003-12-27, and on debian I was happy with 2003-11-11. Are you sure
>> compiling the HEAD version solves the problem?
>
>Though I'm not sure, there are some fixes which are not
>backported to 1.8 yet.

As there were no other suggestions, I try to do my first ruby
compiling... (

Mandrake uses many dist-specific patches to libc. Cannot be the
problem connected with one of these patches?

In article <>,
Ferenc Engard <> wrote:
>Does it affect multithreading (i.e., tk)?
>
>Anyway, it seems that the problem exists only on mandrake, even with
>newer ruby than on my debian box. The latest one was tried is
>2003-12-27, and on debian I was happy with 2003-11-11. Are you sure
>compiling the HEAD version solves the problem?
>
>Nobody uses mandrake here?

I use Mandrake 9.2 (up to date with the latest patches) with a "self
compiled" Ruby 1.8.1 with no problems, and I am messing around with a
Tk application quite happily.

On Wed, 21 Jan 2004, Andre Nathan wrote:
>Ferenc Engard said:
>> As there were no other suggestions, I try to do my first ruby
>> compiling... (
>>
>> Mandrake uses many dist-specific patches to libc. Cannot be the
>> problem connected with one of these patches?
>
>Mandrake has a ruby-tk package. Did you install this one? Also, the
>ruby rpm is not compiled with pthreads enabled (at least the one from
>rpmfind.net). You could try editing the spec file and re-create the
>rpm.

Sorry, I looked on my debian box. On mdk, the ruby and the libtk do
not depend on pthreads.

So, this cannot be the problem. :-(((

We use those packages, and my brother tried compile from the latest
sources which mdk provides. Still crashes...

The program crashes after I start to iterate through on a
DBI::statementHandle with 2-3000 rows, but not always the same place.
Sometimes during the iteration (searching, anyway), sometimes after
it. I suspect to the GC, too, as many objects are created during this
process.

On Tue, 20 Jan 2004, Mike Stok wrote:
>In article <>,
>Ferenc Engard <> wrote:
>>Does it affect multithreading (i.e., tk)?
>>
>>Anyway, it seems that the problem exists only on mandrake, even with
>>newer ruby than on my debian box. The latest one was tried is
>>2003-12-27, and on debian I was happy with 2003-11-11. Are you sure
>>compiling the HEAD version solves the problem?
>>
>>Nobody uses mandrake here?
>
>I use Mandrake 9.2 (up to date with the latest patches) with a "self
>compiled" Ruby 1.8.1 with no problems, and I am messing around with a
>Tk application quite happily.
>
>[mike@ratdog mike]$ cat /etc/redhat-release
>Mandrake Linux release 9.2 (FiveStar) for i586
>[mike@ratdog mike]$ rpm -qa | grep '^tk-'
>tk-8.4.2-1mdk

> > > > Here are the backtraces (sorry about the long mail):
> > >
> > > All seem related with GC. I guess it might be fixed in CVS
> > > HEAD, or disapper by configuring with --disable-pthread.
> >
> > Does it affect multithreading (i.e., tk)?
>
> It should have worked before --enable-pthread was introduced.
>
> > Anyway, it seems that the problem exists only on mandrake, even with
> > newer ruby than on my debian box. The latest one was tried is
> > 2003-12-27, and on debian I was happy with 2003-11-11. Are you sure
> > compiling the HEAD version solves the problem?
>
> Though I'm not sure, there are some fixes which are not
> backported to 1.8 yet.

Compiling from the yesterday's snapshot (with mdk patches) do not
produce these errors. Thank you very much for your help!

Share This Page

Welcome to The Coding Forums!

Welcome to the Coding Forums, the place to chat about anything related to programming and coding languages.

Please join our friendly community by clicking the button below - it only takes a few seconds and is totally free. You'll be able to ask questions about coding or chat with the community and help others.
Sign up now!