Re: [Fxruby-users] Segfaults

[Gilles F. <gil...@fr...>]

Me again...

Here is a valgrind output for the first bug reported in my previous=20
mail. It seems to be related with GCing FXTableItem. Tell me if it is=20
sufficient for you to find the actual problem.
_gilles.

maison:~/Mirrage$ valgrind --suppressions=3Druby.supp=20
--gen-suppressions=3Dyes ruby application.rb
=3D=3D11753=3D=3D Memcheck, a memory error detector for x86-linux.
=3D=3D11753=3D=3D Copyright (C) 2002-2004, and GNU GPL'd, by Julian Sewar=
d.
=3D=3D11753=3D=3D Using valgrind-2.1.1, a program supervision framework f=
or=20
x86-linux.
=3D=3D11753=3D=3D Copyright (C) 2000-2004, and GNU GPL'd, by Julian Sewar=
d.
=3D=3D11753=3D=3D For more details, rerun with: -v
=3D=3D11753=3D=3D
=3D=3D11753=3D=3D Invalid read of size 4
=3D=3D11753=3D=3D    at 0x3CA4EB63: FXObject::getClassName() const (in=20
/usr/lib/libFOX-1.0.so.0.0.42)
=3D=3D11753=3D=3D    by 0x3C7BE6DA: FXRbTableItem::markfunc(FXTableItem*)=
 (in=20
/usr/local/lib/site_ruby/1.8/i386-linux/fox.so)
=3D=3D11753=3D=3D    by 0x3C077002: (within /usr/lib/libruby1.8.so.1.8.1)
=3D=3D11753=3D=3D    by 0x3C076B53: (within /usr/lib/libruby1.8.so.1.8.1)
=3D=3D11753=3D=3D  Address 0x3D94CA60 is 0 bytes inside a block of size 2=
0 free'd
=3D=3D11753=3D=3D    at 0x3C021A3C: operator delete(void*) (vg_replace_ma=
lloc.c:129)
=3D=3D11753=3D=3D    by 0x3CA7E843: FXTableItem::~FXTableItem() (in=20
/usr/lib/libFOX-1.0.so.0.0.42)
=3D=3D11753=3D=3D    by 0x3CA86634: FXTable::~FXTable() (in=20
/usr/lib/libFOX-1.0.so.0.0.42)
=3D=3D11753=3D=3D
=3D=3D11753=3D=3D ---- Print suppression ? --- [Return/N/n/Y/y/C/c] ---- =
n
=3D=3D11753=3D=3D
=3D=3D11753=3D=3D Invalid read of size 4
=3D=3D11753=3D=3D    at 0x3CA4EB66: FXObject::getClassName() const (in=20
/usr/lib/libFOX-1.0.so.0.0.42)
=3D=3D11753=3D=3D    by 0x3C7BE6DA: FXRbTableItem::markfunc(FXTableItem*)=
 (in=20
/usr/local/lib/site_ruby/1.8/i386-linux/fox.so)
=3D=3D11753=3D=3D    by 0x3C077002: (within /usr/lib/libruby1.8.so.1.8.1)
=3D=3D11753=3D=3D    by 0x3C076B53: (within /usr/lib/libruby1.8.so.1.8.1)
=3D=3D11753=3D=3D  Address 0x3 is not stack'd, malloc'd or free'd
=3D=3D11753=3D=3D
=3D=3D11753=3D=3D ---- Print suppression ? --- [Return/N/n/Y/y/C/c] ---- =
n
./donnees.rb:20: [BUG] Segmentation fault
ruby 1.8.1 (2004-02-03) [i386-linux]

=3D=3D11753=3D=3D
=3D=3D11753=3D=3D Process terminating with default action of signal 6 (SI=
GABRT):=20
dumping core
=3D=3D11753=3D=3D    at 0x3C1AD571: kill (in /lib/libc-2.3.2.so)
=3D=3D11753=3D=3D    by 0x3C01AB7B: gsignal (vg_intercept.c:65)
=3D=3D11753=3D=3D    by 0x3C1AE837: abort (in /lib/libc-2.3.2.so)
=3D=3D11753=3D=3D    by 0x3C055D90: rb_bug (in /usr/lib/libruby1.8.so.1.8=
.1)
=3D=3D11753=3D=3D
=3D=3D11753=3D=3D ERROR SUMMARY: 2 errors from 2 contexts (suppressed: 68=
2232=20
from 10)
=3D=3D11753=3D=3D malloc/free: in use at exit: 4098868 bytes in 80068 blo=
cks.
=3D=3D11753=3D=3D malloc/free: 446726 allocs, 366658 frees, 13775889 byte=
s=20
allocated.
=3D=3D11753=3D=3D For a detailed leak analysis,  rerun with: --leak-check=
=3Dyes
=3D=3D11753=3D=3D For counts of detected errors, rerun with: -v
Abandon
maison:~/Mirrage$

Gilles Filippini a =E9crit :
> Hi Lyle,
>=20
> It's been long time since I've tried FXRuby intensively :o)
> I'm back with the same kind of segfaults I had then.
>=20
> For example FXEvent appears corrupted after a while in an onPaint=20
> callback. I don't have a simple test case yet. I'll try to narrow the=20
> probelm using valgrind. The bug vanishes when GC is disabled.
>=20
> Just to try, I've launched an old test case (not related to the above=20
> bug) I used when there were problems with TreeList items. Segfault=20
> again. I send it to you by private mail.
>=20
> My box runs :
> - Debian/sarge GNU/Linux
> - fox-1.0.42
> - ruby 1.8
> - FXRuby 1.0.28
> HTH.
>=20
> _gilles.
>=20