[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: How do you swarm guys make valgrind work?
From: |
Leland Hovey |
Subject: |
Re: How do you swarm guys make valgrind work? |
Date: |
Tue, 28 Jan 2003 08:22:51 -0500 (EST) |
Let's see if valgrind works for you for the simplest case first, and then
...
1. I'm using valgrind 1.0.3, RedHat 7.2, and Swarm-2.1.1.
2. Valgrind was installed from an rpm.
3. I'm testing in the directory swarmapps-2.1.1/tutorial/simpleObjCBug.
4. I used the command "valgrind -v --leak-check=yes bug".
-Is there a way to duplicate this?
On Mon, 27 Jan 2003, Paul E. Johnson wrote:
> Several people recommended I try Valgrind as a way to find the memory
> problem in the program that one of the users sent me.
>
> I've developed this weird problem with a Swarm list, where I only put in
> Person objects, but then after a while, the program crashes saying the
> IndexLinked_List does not answer to getAge, one of the methods in
> Person. So, obviously, somehow I'm getting an index written where I
> should have a person, and I can't for the life of me figure out why.
>
> I downloaded the last stable Valgrind 1.0.4 as well as their development
> versions and I get the same result either way. I can't even get my
> program to start up. Obviously, on these RedHat Linux systems, I need
> some special exclusions to make this work? Can anybody who gets it to
> work tell me exactly how?
>
> I've tried this on both Redhat 7.3 (glibc 2.2) and Redhat 8.0 (with the
> fishy glibc 2.3) and the same happens. Same with my programs or heatbugs.
>
> $ /usr/local/valgrind/bin/valgrind ./v6
> ==1569== Memcheck, a.k.a. Valgrind, a memory error detector for x86-linux.
> ==1569== Copyright (C) 2002, and GNU GPL'd, by Julian Seward.
> ==1569== Using valgrind-1.9.3, a program instrumentation system for
> x86-linux.
> ==1569== Copyright (C) 2000-2002, and GNU GPL'd, by Julian Seward.
> ==1569== Estimated CPU clock rate is 550 MHz
> ==1569== For more details, rerun with: -v
> ==1569==
> Double word alignment of malloc allocations not guaranteed
> on local machine architecture.
> Please report to address@hidden
> Standard fixup taken, execution continuing...
> ==1569== Invalid write of size 4
> ==1569== at 0x403CE545: _i_Zone_c__allocIVars_
> (/home/pauljohn/LinuxDownloads/redhat/BUILD/swarm-2.1.141.20021019/src/defobj/Zone.m:183)
> ==1569== by 0x403CCF86: initModules
> (/home/pauljohn/LinuxDownloads/redhat/BUILD/swarm-2.1.141.20021019/src/defobj/Program.m:140)
> ==1569== by 0x403CD862: _obj_initModule
> (/home/pauljohn/LinuxDownloads/redhat/BUILD/swarm-2.1.141.20021019/src/defobj/Program.m:260)
> ==1569== by 0x401FEFE0: _c_SwarmEnvironment__createBegin
> (/home/pauljohn/LinuxDownloads/redhat/BUILD/swarm-2.1.141.20021019/src/SwarmEnvironment.m:90)
> ==1569== Address 0x18 is not stack'd, malloc'd or free'd
> Segmentation fault
>
>
>
> --
> Paul E. Johnson email: address@hidden
> Dept. of Political Science http://lark.cc.ukans.edu/~pauljohn
> University of Kansas Office: (785) 864-9086
> Lawrence, Kansas 66045 FAX: (785) 864-5700
>
>
>
> ==================================
> Swarm-Support is for discussion of the technical details of the day
> to day usage of Swarm. For list administration needs (esp.
> [un]subscribing), please send a message to <address@hidden>
> with "help" in the body of the message.
>
==================================
Swarm-Support is for discussion of the technical details of the day
to day usage of Swarm. For list administration needs (esp.
[un]subscribing), please send a message to <address@hidden>
with "help" in the body of the message.