Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 19 Dec 1998 16:07:11 -0800
From:      John-Mark Gurney <gurney_j@efn.org>
To:        John-Mark Gurney <gurney_j@resnet.uoregon.edu>
Cc:        FreeBSD Hackers <freebsd-hackers@FreeBSD.ORG>
Subject:   Re: _rtld_bind_start Segfault
Message-ID:  <19981219160711.16076@hydrogen.nike.efn.org>
In-Reply-To: <19981219122025.22295@hydrogen.nike.efn.org>; from John-Mark Gurney on Sat, Dec 19, 1998 at 12:20:25PM -0800
References:  <19981219122025.22295@hydrogen.nike.efn.org>

next in thread | previous in thread | raw e-mail | index | archive | help
John-Mark Gurney scribbled this message on Dec 19:
>    for (j = 0; j < MAX; j++) 
>    { for (i = 0; i < MAX; i++); 
				^
I found the problem....  i was 20 for the next two lines overwriting
environ's data, and the printf at the begining was cacheing the results
of the getenv calls that were necessary...

>      { A[i][j] = i - j;
>        B[i][j] = i + j;
>      }
>    }

the reason I wrote this message is that I run across another bug in
another program that linking the program -static fixed a problem where
it's child process would suddenly start to segfault... and the segfault
was in strcpy...  at one time the address managed to be reported as
_rtld_bind_start.... and I know for a FACT that the addresses were
correct, as I set a break point at the strcpy, verified that both the
destination buffer was an automatic char [512], and the source was a
seven character string...  I would try to advance to the next line and
it would segfault...

debuging this program is hard as the bug doesn't show up till 400+megs
into the data stream, and I don't have enough disk space currently to
store it on disk (I will in a few hours)...  and it takes ~45 minutes
to read the 400megs from tape...

sorry to bother you guys...

-- 
  John-Mark Gurney                              Voice: +1 541 684 8449
  Cu Networking					  P.O. Box 5693, 97405

  Live in Peace, destroy Micro$oft, support free software, run FreeBSD
	    Don't trust anyone you don't have the source for

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19981219160711.16076>