On Fri, Feb 14, 2020 at 02:33:15PM -0700, Christoph Junghans wrote:
On Fri, Feb 14, 2020 at 10:37 AM Dan Horák <dan(a)danny.cz>
wrote:
>
> On Fri, 14 Feb 2020 10:28:10 -0700
> Christoph Junghans <junghans(a)votca.org> wrote:
>
> > >>
> > >> In your case procps-ng package seems to be miscompiled (or run on
> > >> an incopatible hardware). I recommend getting a shell in the mock
> > >> enviroment (mock --shell) and investigeting whether the ps program
> > >> works there).
> > >
> > > Ok, I will try that and report back.
> > It is indeed broken in shell as well:
> > <mock-chroot> sh-5.0# ps
> >
> > Signal 4 (ILL) caught by ps (3.3.15).
> > /usr/bin/ps:ps/display.c:66: please report this bug
> > Segmentation fault (core dumped)
>
> works (no crash) on my Power9 system, but it could be a P9 instruction
> sneaked into the binary and crashing on Power8 systems. I'll take a
> look, but if you could file a bug (with me in CC), it would be helpful.
just to make sure, I am running this in mock on the following system:
$ cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 142
model name : Intel(R) Core(TM) i7-7567U CPU @ 3.50GHz
Then you actually run the PowerPC ps binary in QEMU emulator. Could you show
the /proc/cpuinfo from inside of the mock environment?
-- Petr