git problems

Chuck Robey chuckr at
Wed Jun 4 14:22:24 UTC 2008

Hash: SHA1

Robert Watson wrote:
> On Tue, 3 Jun 2008, Ed Schouten wrote:
>> * Chuck Robey <chuckr at> 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 at mailing list
> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe at"

Version: GnuPG v2.0.4 (FreeBSD)
Comment: Using GnuPG with Mozilla -


More information about the freebsd-hackers mailing list