Date: Sun, 27 Jul 2014 14:40:56 +0100 From: Matthew Seaman <m.seaman@infracaninophile.co.uk> To: freebsd-ports@freebsd.org Subject: Re: PKG 3.1.0 update - Segmentation fault: 11 Message-ID: <53D50168.1030505@infracaninophile.co.uk> In-Reply-To: <53D4FD00.9050204@sorbs.net> References: <53D4CE4A.3040208@webrz.net> <20140727111949.GH50802@ivaldir.etoilebsd.net> <20140727123035.GR34525@albert.catwhisker.org> <53D4F2CF.4040501@sorbs.net> <20140727125528.GS34525@albert.catwhisker.org> <53D4FD00.9050204@sorbs.net>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --fS4JOmibnT3VkBaLG65fjI5pTbq3xmekK Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 27/07/2014 14:22, Michelle Sullivan wrote: > Unless the fault smashed the stack often you can find what the > problem/cause was. If the stack is smashed you're screwed. >=20 > gdb <path to binary> <path to core> >=20 > Commands immediately useful: >=20 > backtrace full (alias: bt full) > frame <number> for which you want to examine > if you get a line number/code, 'l' (el) will give the 5 lines eithersid= e > If threaded select each thread before the frame to see what was > happening in each thread. >=20 > If I remember correctly - it's been several years since I last used gdb= ;-) >=20 > If you want to catch a smashed stack problem run the binary in gdb: >=20 > gdb <path to command> >=20 > Then: >=20 > set args <what ever is approrpiate> > run >=20 > When it faults most of the time you'll get the stack just prior to the > smashing - though I have had some really bad ones when even gdb cored o= ut.. >=20 > If the process forks out, you will need to use follow-fork.. Actually pkg(8) pretty much always forks itself -- run it with the '-d' flag to prevent that. However, this particular crash is something we've received plenty of reports about. I believe bapt has a fix just about ready, but he's AFK for a little while. If you'ld like to help with testing and stuff, might I suggest joining #pkgng on freenode IRC? Cheers, Matthew --=20 Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey JID: matthew@infracaninophile.co.uk --fS4JOmibnT3VkBaLG65fjI5pTbq3xmekK Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.20 (Darwin) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQJ8BAEBCgBmBQJT1QFpXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ2NTNBNjhCOTEzQTRFNkNGM0UxRTEzMjZC QjIzQUY1MThFMUE0MDEzAAoJELsjr1GOGkAT/GIP/RZnfH8o6nrWpOwiVaiRjzYe /BXYGqDH3A2ggiJIY/aYpYcag3s+JXhoJZuzfkWedmSidvktMcVySuXGU1B0aioP QLGLMTkyGbGRuvgYRxIiBfLl3ljmc2IosWxIKBLItbjb0mPqfBlofoZDbVjR7r+B MA6wNb5joOCBFpglrVKvqiG3uktMKDuTYUIu0FCU1PGq0e+2o57C5FGVbYyYGW2C 8UgQn36HXAqmJbah9lc6YmxFGK7henSFNpYU4nu91OjfdvZQPGqSYU0wFDEZCstU U/0I/2NkPPKX3dUyijJaz6wZ1JdVVF7mrW0LfUbrFqywePOd9hlVNAFhtbdlS0IJ M1ufcc2RksL2r8vn9tQe7EbfH2D2RSJlRBKnnRYIvzL/wfcO4n7hO/4grWsL+iBI Z+TK61zFO7TTxemT5yvUXLH8y1D6fGD3d3pIoz72eFM+TSrbo7FADE7bXlWHsY/0 er6L83AJR9D1v720bJTrcAO5IoQLO10CVCbQUpauZSKdJia37Rg0+FW5X6BlSGeP 7Y1phXsFG5qo8vnXJyfzSusvZKrNyKEwljKO8eI9J2mr7aexv1ej8B8ye2MV9Ruy FpJKJfu3rpD2PeG7ym7roQrZTTF/MyjTxWEDX3WyYKA9ocagul4mueQEsgDO+cMr jdC6I4vcUgqt43nOVnnq =9rSz -----END PGP SIGNATURE----- --fS4JOmibnT3VkBaLG65fjI5pTbq3xmekK--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?53D50168.1030505>