Date: Sun, 27 Jul 2014 05:55:28 -0700 From: David Wolfskill <david@catwhisker.org> To: Michelle Sullivan <michelle@sorbs.net> Cc: Baptiste Daroussin <bapt@FreeBSD.org>, FreeBSD Ports ML <freebsd-ports@freebsd.org> Subject: Re: PKG 3.1.0 update - Segmentation fault: 11 Message-ID: <20140727125528.GS34525@albert.catwhisker.org> In-Reply-To: <53D4F2CF.4040501@sorbs.net> References: <53D4CE4A.3040208@webrz.net> <20140727111949.GH50802@ivaldir.etoilebsd.net> <20140727123035.GR34525@albert.catwhisker.org> <53D4F2CF.4040501@sorbs.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--FiqEyLLt06qkB6ow Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Jul 27, 2014 at 02:38:39PM +0200, Michelle Sullivan wrote: > ... > By any chance is there a core file around releated to this, and if so > was the binary that faulted unstripped? In each of the 3 cases, I find a /usr/ports/ports-mgmt/pkg/pkg-static.core file g1-252(9.3-S)[4] sudo file pkg-static.core Password: pkg-static.core: ELF 32-bit LSB core file Intel 80386, version 1 (FreeBSD),= FreeBSD-style, from '-static' g1-252(9.3-S)[5]=20 > I'd be interested in seeing the backtrace... Well, given it was a segmentation fault, it's not clear to me that I'd be able to find much of value -- I'm way out of practice using gdb, and by the nature of a segmentation fault (or what caused it, anyway), something is pretty confused by the time the fault is discovered. > (I'm not using 1.3 or even NG on any of my production > systems at the moment because I personally don't trust it yet (I have 57 > complex systems and if they screw up I end up rebuilding the OS from > scratch) so I'd be happy to take a look at any cores an unstripped > binaries to see if I can work out why people see this occasionally...=20 > Sounds like you have 3 identical systems which 2 worked no problems the > third faulted .. this is obviously not good and needs to be fixed, so > will give another pair of eyes at the problem. Err... no.... I have 5 system in total; 2 haven't failed because I haven't tried to update them yet: if they fail, I don't have access to email (or much of anything else); more critially, neither does my spouse -- and I value domestic tranquility. Of the 3 failures, 2 were on i386; one on amd64. They are all running stable/9 @r269090 (and the 2 that I haven't upgraded yet would normally be upgraded to that point before I start messing with ports on them). I'll be happy to provide any information about this that I can. Peace, david --=20 David H. Wolfskill david@catwhisker.org Taliban: Evil cowards with guns afraid of truth from a 14-year old girl. See http://www.catwhisker.org/~david/publickey.gpg for my public key. --FiqEyLLt06qkB6ow Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ8BAEBCgBmBQJT1Pa+XxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ4RThEMDY4QTIxMjc1MDZFRDIzODYzRTc4 QTY3RjlDOERFRjQxOTNCAAoJEIpn+cje9Bk7ongP/jl4ilWLv/4YeLmxzr0Snyz4 VRzNUx3MvX6QSik9AYT/G3t4zXwzUaczUka7NfOJNmaq/afV1Lm93J/cfKftJ8HP LT+uwu4NSBp1e8u2+rMCccgV8jOVG4Ef8AFZx96C5baD5xwm6OZqzrBv+Ni3jm7z cKjMfmJEx+U9XqA8PbyEmXXxwpcAwdPAztiAfVMJCzdgD7SOPeDcUyThhXuSzhzV Ex7gb3CohgKtKRtTWAITRXbrfJ1qQn+2/zmXNk/5HBCZAVXsgBr2P0e0meX3DjKk uy26cQ5Mfz3l8z03l3WN8IcPac4ndj7tz+Sa7nAWoBSLzvSaVj0Li04sau2hoEOe ZHYBr0UibavdiPc8+4ErOVdbqh6tcoHzFREz6P6VIvhonlwp+P0Lzy9+wLcU3qJ9 X2Q+slo/1QrzICrI2yA3Bu0wcytRqUOJD5pw9Rb8TJruw5LGNFeU7nE6tzpyGCPu oXcX98+HE0trdptUbLHpcot2olIPy28dxVMqY/HdC65UHzSs9oURnEQD4rYySu2x d1066eYRif/Y05pHTXB1BYgdke13Huc1LMByUMdPaXFDsQGVQeqt0H9cqBNksO2D yyNnXork6I5YvecarnkwxAqWcbyQnDH9k6yhg1Qry7mcEbUQrU8ICbXM6HEzZt1R BFJvLmlt/uSlHTJ27IVF =ce4g -----END PGP SIGNATURE----- --FiqEyLLt06qkB6ow--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140727125528.GS34525>