Date: Wed, 4 Jun 2008 18:48:14 +0400 From: Eygene Ryabinkin <rea-fbsd@codelabs.ru> To: Chuck Robey <chuckr@telenix.org> Cc: FreeBSD-Hackers <freebsd-hackers@freebsd.org> Subject: Re: Re: git problems Message-ID: <L4F%2B2AmHcL4Uix8Rch4QiSpqQwc@RzJPyOBFuChtvuf1tf1krA3%2BwkI> In-Reply-To: <4846A77B.9060603@telenix.org> References: <4845AC84.6040407@telenix.org> <TbQi51CAu4j4cFDkKULTI53ON0k@8ZdGo3QYE5K669Y/W2Z6ZKf2XtY> <4846A77B.9060603@telenix.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Chuck, Wed, Jun 04, 2008 at 10:32:27AM -0400, Chuck Robey wrote: > > Any possibility of using ElectricFence (devel/ElectricFence) > > for chasing memory-related troubles? > > Now that I have gdb working with me again, I am checking the git-fetch image to > see where it got lost. If I must bring a tool such as ElectricFence I, I guess > I must, just I'm a bit irritated that the git build has one of those make > "improvements" (NOT) that instead of telling you the buid line, just gives you > "CC sourcename.c" which for anyone who knows code is just irritating, not any > sort of help at all. No problems, just issue 'make V=1' instead of just 'make' in the <ports>/devel/git -- it will give you all flags and will eliminate the fancies. And 'make V=1 CFLAGS="-O0 -g"' will produce unoptimized binary with debug symbols that can be directly traced by gdb with all symbols and right (unoptimized, as in the sources) code paths. For the ElectricFence -- it dumps core just after startup, I don't know why. So it is not very much usable now, at least for me. Thank you. -- Eygene
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?L4F%2B2AmHcL4Uix8Rch4QiSpqQwc>