Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 27 Jul 2014 06:40:27 -0700
From:      David Wolfskill <david@catwhisker.org>
To:        Michelle Sullivan <michelle@sorbs.net>
Cc:        FreeBSD Ports ML <freebsd-ports@freebsd.org>
Subject:   Re: PKG 3.1.0 update - Segmentation fault: 11
Message-ID:  <20140727134027.GT34525@albert.catwhisker.org>
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

--9hshNW4m6zn79FF/
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sun, Jul 27, 2014 at 03:22:08PM +0200, Michelle Sullivan wrote:
> ...
> > 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 (FreeB=
SD), FreeBSD-style, from '-static'
> > g1-252(9.3-S)[5]=20
> >  =20
>=20
> Doesn't appear stripped..
> >  =20
> >> I'd be interested in seeing the backtrace...
> ...
> >  =20
> 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>

Well, you see, that's part of the problem:  I'm not at all sure
where the executable in question actually is.  (There is nothing
named "pkg-static" in my execution search path.)  If I assume(!)
that it's in the port's staging area:

sudo gdb ./pkg-static ../../../../../pkg-static.core
=2E..
Core was generated by `pkg-static'.
Program terminated with signal 11, Segmentation fault.
#0  0x080b6cdc in ?? ()
(gdb) bt
#0  0x080b6cdc in ?? ()
#1  0x28404360 in ?? ()
#2  0x28442220 in ?? ()
#3  0x00000000 in ?? ()
(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>

Yes; well... that presumes a familiarity with the "internal workings" of
pkg which I don't have (and, in all honesty, don't want to have).

> 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 out=
=2E.

Indeed: one gets into "interesting" issues of figuring out what is
actually reliable information (and what is merely debris).

> ...


Back on the original topic, I was able to get pkg-1.3.1 installed and
apparently functioning on one system (a headless build machine -- which
has the least number of ports inistalled).

What I ended up doing that seems to have "worked"(?) was:
* mv /var/db/pkg{,.save}
* mkdir /var/db/pkg
* cp -pr /var/db/pkg.save/local.sqlite /var/db/pkg
* portmaster -d ports-mgmt/pkg
  This builds OK, then dies in installation a little peculiarly:

=2E..
=3D=3D=3D=3D> Compressing man pages (compress-man)
=3D=3D=3D>  Installing for pkg-1.3.1
=3D=3D=3D>  Checking if ports-mgmt/pkg already installed
=3D=3D=3D>   An older version of ports-mgmt/pkg is already installed (apr-1=
=2E5.1.1.5.3_
=2E..[list of every installed port on the machine]...)
      You may wish to ``make deinstall'' and install this port again
      by ``make reinstall'' to upgrade it properly.
      If you really wish to overwrite the old port of ports-mgmt/pkg
      without deleting it first, set the variable "FORCE_PKG_REGISTER"
      in your environment or the "make install" command line.
*** [check-already-installed] Error code 1

* cd /usr/ports/ports-mgmt/pkg && make reinstall
  Which seems to have made constructive use of the port just built (vs.
  building it all over yet again)a nd installed it.

I don't yet know how disruptive this has been to ... well anything
(e.g., the current status of installed ports; ability to update ports in
the future; ...).

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.

--9hshNW4m6zn79FF/
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQJ8BAEBCgBmBQJT1QFKXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w
ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ4RThEMDY4QTIxMjc1MDZFRDIzODYzRTc4
QTY3RjlDOERFRjQxOTNCAAoJEIpn+cje9Bk7d1QP/iajQYn+/la9zDbXlZ1xYMh5
vB7sHRqyQUajByvb53TUz237iEQSQmc8A6vLisdlQNnOsiUgU8cpCySdCVq2qbqg
HvhTX4bqNWiZ41TGqMwoI5+79LHEgH1h3osRUvcI24gwgQloJ9P0+YFUVZTIBBe4
P5hmK4SZTdY+JvXVTQyRG5GmhZtxPou5uTFJn1cYIoyJfYuDjjwfo23wS/LS21eg
S11C9UiGPVZm8v9mM1W/ceF5WEL5m89AJwOcDy9hML+OGIfyTjkMEQPa7T5VjNa3
ISyZpIw13JE5bnMyFwcvNUxP3lB3tB7ZFJLcTCI82Oc3pQcfBeGwmhfV146P4NRs
i/mqdISMJazU241ndjrfN8Lb8BxrR9+42FIGbM3MV+g35SuyiAV6+ED6igaEdT9B
vSWOBrOqE/q7kXBrdDV6HS7dFiKX8onDgVFahNcvbScr4hK54TwcTGD9p47qwYot
ktGqAOAiQOnxYv54RgrtNeWH4VesCT4Resp2F48kLLzgsoYAxssJ1/HTqwVJlRJg
Jny6m/EHHZadMP+kmF6A3386yKp32hl97ehHGTT/LCFGcY5mE+v3V3tI1bLgxBtj
zghlMirXkmaz7xTQ20t1SoUJLb6Szh0k/g1ssbcxbnkFpojDNz36ncbTFS8hbWV1
c4cereXdxRM2BiHtNlS5
=pRZK
-----END PGP SIGNATURE-----

--9hshNW4m6zn79FF/--



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