Date: Fri, 5 Oct 2018 08:20:07 +0200 From: Matthias Apitz <guru@unixarea.de> To: freebsd-current@freebsd.org, kde@freebsd.org Subject: Re: debugging a run of poudriere-bulk Message-ID: <20181005062007.GA11816@sh4-5.1blu.de> In-Reply-To: <0c07c460-4f3a-2fbb-d236-e97c77e74b4d@ShaneWare.Biz> References: <20181003114114.GA4946@c720-r314251> <0c07c460-4f3a-2fbb-d236-e97c77e74b4d@ShaneWare.Biz>
next in thread | previous in thread | raw e-mail | index | archive | help
El día Thursday, October 04, 2018 a las 01:14:55PM +0930, Shane Ambler escribió: > > How can I enter the jail interactively in the moment after the crash to rerun and > > debug pkg-static? > > Using > > poudriere testport -j <jname> -p <portstree> -i -o <cat/port> > > will drop you into the jail after the build stops, you then rerun make > manually, check build logs... Logging out will then continue on and > clean up the jail. You can also use -I instead of -i and it leaves the > jail in place so you can manually connect to and stop the jail. > > Note that poudriere uses a clean jail with only deps listed for the > port, you can add extra BUILD_DEPENDS to get extra ports (gdb valgrind) > installed with the test build. Thanks! One should read man pages completely in advance and not only the part of 'poudriere bulk ...'. I did so and in nthis case the crash occurs *after* the package is complete: ... ====> Checking for pkg-plist issues (check-plist) ===> Parsing plist ===> Checking for items in STAGEDIR missing from pkg-plist ===> Checking for items in pkg-plist which are not in STAGEDIR ===> No pkg-plist issues found (check-plist) =>> Checking for staging violations... done =======================<phase: package >============================ ===> Building package for kde-workspace-kde4-4.11.22_26 file sizes/checksums [2126]: .......... done packing files [2126]: .......... done packing directories [0]: . done =========================================================================== =>> Recording filesystem state for preinst... done =======================<phase: install >============================ ===> Installing for kde-workspace-kde4-4.11.22_26 ===> Checking if kde-workspace-kde4 already installed ===> Registering installation for kde-workspace-kde4-4.11.22_26 Child process pid=75639 terminated abnormally: Segmentation faul *** Error code 139 Stop. make: stopped in /usr/ports/x11/kde-workspace-kde4 =======================<phase: Interactive >============================ [00:13:29] Installing packages [00:13:29] Installing run-depends for x11/kde-workspace-kde4 | kde-workspace-kde4-4.11.22_26 # ls -l /wrkdirs/usr/ports/x11/kde-workspace-kde4/work/pkg/kde-workspace-kde4-4.11.22_26.txz -rw-r--r-- 1 nobody wheel 18338720 Oct 4 14:02 /wrkdirs/usr/ports/x11/kde-workspace-kde4/work/pkg/kde-workspace-kde4-4.11.22_26.txz Poudriere installs the package 'pkg' into the jail to could make use of 'pkg-static' (and other tools). Maybe it would be an idea to create outside a special version of this package which have a special version of 'pkg-static' in this, for example a shellsript with the name pkg-static which is something like: #!/bin/sh echo $0 $* > /tmp/pkg-static-args.$$ truss -o /tmp/pkg-static.$$ /usr/local/sbin/pkgstatic.exec $* to get more information about the crash. Other ideas? matthias -- Matthias Apitz, ✉ guru@unixarea.de, http://www.unixarea.de/ +49-176-38902045 Public GnuPG key: http://www.unixarea.de/key.pub October, 7 -- The GDR was different: Peace instead of Bundeswehr and wars, Druschba instead of Nazis, to live instead of to survive.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20181005062007.GA11816>