Date: Wed, 04 Jun 2008 10:28:45 -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: <4846A69D.4000105@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. This is really replying to my own question, because I found what I was missing. I have'nt done any troubleshooting for a long while now (health, down for some years) and the last time I did it, if you had a core file in the same directory as the binary and the sources, gdb would know where to find the symbols on it's own, but it looks like that's changed. Once I explicitly gave the symbols, th8ings began to work ok, so you can stop worrying about my missing stack frames. Now that I have that, I have also the ability to find out where git-fetch died, and I will pretty quickly, that ought to help some. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIRqVvz62J6PPcoOkRAoKcAJ9c5WFhKf0NkOCgfNFO53jEWpsPUwCdErw4 RY8Ry6WQpgwOKVAPoe+mOUs= =M+hX -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4846A69D.4000105>