|
From: Mark P. <pro...@ac...> - 2005-02-14 19:31:22
|
Hi, I am just starting to use valgrind under FreeBSD, and using it to memory check a Ruby script for a suspected gc problems. Unfortunately, I seem to be consistently crashing valgrind (the script is threaded and uses sockets): 11:25 (kant)$ vgm ruby test3.rb ==26229== Memcheck, a memory error detector for x86-linux. ==26229== Copyright (C) 2002-2004, and GNU GPL'd, by Julian Seward. ==26229== Using valgrind-2.1.2.CVS, a program supervision framework for x86-linux. ==26229== Copyright (C) 2000-2004, and GNU GPL'd, by Julian Seward. ==26229== For more details, rerun with: -v ==26229== --26229-- INTERNAL ERROR: Valgrind received a signal 11 (SIGSEGV) - exiting --26229-- si_code=0xC Fault EIP: 0xB8032609 (); Faulting address: 0x4FFF9F50 valgrind: the `impossible' happened: Killed by fatal signal Basic block ctr is approximately 1550000 ==26229== at 0xB802D8D5: (within /usr/local/lib/valgrind/stage2) ==26229== by 0xB802D8D4: (within /usr/local/lib/valgrind/stage2) ==26229== by 0xB802D8EC: vgPlain_core_panic (in /usr/local/lib/valgrind/stage2) ==26229== by 0xB8034354: (within /usr/local/lib/valgrind/stage2) sched status: Thread 1: status = Runnable, associated_mx = 0x0, associated_cv = 0x0 ==26229== at 0x3C0B7DF7: (within /lib/libc.so.5) ==26229== by 0x3C24A6E1: init_inetsock_internal (socket.c:962) ==26229== by 0x805BDBE: rb_ensure (eval.c:5196) ==26229== by 0x3C24A849: init_inetsock (socket.c:1003) Any ideas? I tried the '--run-libc-freeres=no' on the off chance that it was a libc issue, and no difference. Regards, -- -mark. (probertm at acm dot org) |
|
From: David E. <tw...@us...> - 2005-02-14 20:20:37
|
On Mon, 2005-02-14 at 11:31 -0800, Mark Probert wrote:
> Hi,
>
> I am just starting to use valgrind under FreeBSD, and using it to memory check
> a Ruby script for a suspected gc problems. Unfortunately, I seem to be
> consistently crashing valgrind (the script is threaded and uses sockets):
This may not be what you want to hear, but as it's a Ruby script I hope
portability is not a big problem:
Grab a Linux box and run valgrind there! :-)
--
Regards,
-\- David Eriksson -/-
SynCE - http://synce.sourceforge.net
ScummVM - http://scummvm.sourceforge.net
Desquirr - http://desquirr.sourceforge.net
|
|
From: Mark P. <pro...@ac...> - 2005-02-14 20:31:01
|
Hi .. On Monday 14 February 2005 12:20, David Eriksson wrote: > On Mon, 2005-02-14 at 11:31 -0800, Mark Probert wrote: > > Hi, > > > > I am just starting to use valgrind under FreeBSD, and using it to memory > > check a Ruby script for a suspected gc problems. Unfortunately, I seem > > to be consistently crashing valgrind (the script is threaded and uses > > sockets): > > This may not be what you want to hear, but as it's a Ruby script I hope > portability is not a big problem: > > Grab a Linux box and run valgrind there! :-) Thanks for your note, David. I'll try it once I have a linux box up and going. My real problem is under Solaris, though I am not going to go into that! And, yes, the scripts are portable, so there shouldn't be an issue with running them under Linux. On a related note, are any distros preferred over any other when it comes to this kind of stuff? Or is it all down to the packaging model an individual likes? Regards, -- -mark. (probertm at acm dot org) |
|
From: David E. <tw...@us...> - 2005-02-14 20:47:40
|
On Mon, 2005-02-14 at 12:31 -0800, Mark Probert wrote:
> Hi ..
>
> On Monday 14 February 2005 12:20, David Eriksson wrote:
> > On Mon, 2005-02-14 at 11:31 -0800, Mark Probert wrote:
> > > Hi,
> > >
> > > I am just starting to use valgrind under FreeBSD, and using it to memory
> > > check a Ruby script for a suspected gc problems. Unfortunately, I seem
> > > to be consistently crashing valgrind (the script is threaded and uses
> > > sockets):
> >
> > This may not be what you want to hear, but as it's a Ruby script I hope
> > portability is not a big problem:
> >
> > Grab a Linux box and run valgrind there! :-)
>
> Thanks for your note, David.
>
> I'll try it once I have a linux box up and going. My real problem is under
> Solaris, though I am not going to go into that!
>
> And, yes, the scripts are portable, so there shouldn't be an issue with
> running them under Linux.
>
> On a related note, are any distros preferred over any other when it comes to
> this kind of stuff? Or is it all down to the packaging model an individual
> likes?
Valgrind is written for 32-bit Linux and I would suggest one with a 2.6
kernel, but apart from that the distro you use is mostly a matter of
preference. If you want specific suggestions, send a private mail so I
don't start any distro wars here... :-)
--
Regards,
-\- David Eriksson -/-
SynCE - http://synce.sourceforge.net
ScummVM - http://scummvm.sourceforge.net
Desquirr - http://desquirr.sourceforge.net
|