Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 04 Jun 2008 10:12:55 -0400
From:      Chuck Robey <chuckr@telenix.org>
To:        Robert Watson <rwatson@FreeBSD.org>
Cc:        Ed Schouten <ed@80386.nl>, FreeBSD Hackers <freebsd-hackers@freebsd.org>
Subject:   Re: git problems
Message-ID:  <4846A2E7.2060003@telenix.org>
In-Reply-To: <20080604134830.D49920@fledge.watson.org>
References:  <4845AC84.6040407@telenix.org> <20080603212355.GB64397@hoeg.nl> <20080604134830.D49920@fledge.watson.org>

next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Robert Watson wrote:
> On Tue, 3 Jun 2008, Ed Schouten wrote:
> 
>> * Chuck Robey <chuckr@telenix.org> wrote:
>>> I am having problems with the git out of ports .... git-fetch keeps
>>> on dumping core when I try update of xorg (the initial checkout works
>>> ok). I'm running FreeBSD-current ... does anyone have any idea why
>>> this might be?
>>>
>>> When I try to do a gdb -c corefile on the resulting core image, all i
>>> get is a couple of thousand empty stack frames.  Any idea why that
>>> might be, also?
>>
>> I'm seeing this on HEAD, not RELENG_6. I don't have a backtrace
>> nearby, but it seems to be crash inside free().
> 
> Application memory errors in HEAD but not in a RELENG_ branch are
> frequently a symptom of an application bug unmasked by malloc(3)
> debugging enabled in the development branch but not production
> branches.  It might not hurt to ramp up debugging on your 6.x install to
> see if it starts crashing there was well -- see malloc(3) for details,
> you'll want to create an appropriate malloc.conf.

I didn't see the email where Ed Schouten commented about seeing my problems of
seeing no good stack frames, but Robert, I run only -current here, not RELENG_6,
so I can't do the testing you speak of.  I would want to see if maybe our gcc on
- -current might have been made with a default of emitting no stack frames, which
I would guess might have this effect.

I guess I could test this, and if it's so, recompile all my libraries to undo
that, because I abhor doing things that utterly block any troubleshooting at a
minimal savings elsewhere.



> 
> Robert N M Watson
> Computer Laboratory
> University of Cambridge
> _______________________________________________
> freebsd-hackers@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4 (FreeBSD)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFIRqLnz62J6PPcoOkRAlhFAJsHrHTMVaFCdPcUha+1yaFOYyMxuACfY+ms
jZRd8WCy9PFcwYICmg636y4=
=4PYv
-----END PGP SIGNATURE-----



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