Re: Anyone seeing problems with ifconfig(8) on the RPI with sources from January 5, 2017?

To: port-arm%NetBSD.org@localhost
Subject: Re: Anyone seeing problems with ifconfig(8) on the RPI with sources from January 5, 2017?
From: Brian Buhrow <buhrow%nfbcal.org@localhost>
Date: Thu, 5 Jan 2017 14:28:33 -0800

	hello.  Following up on my post, here is some additional information.
Below are the last few lines of a ktrace of /sbin/ifconfig.  It looks like
some kind of signal setup  problem, but I haven't looked up the bad address
yet.  Does this shed any light on the trouble for anyone?

Also, gdb(1) exhibits the same behavior.

-thanks
-Brian

  1049      1 ifconfig CALL  __sigprocmask14(1,0x7fea5ee8,0x7fea5fd8)
  1049      1 ifconfig RET   __sigprocmask14 0
  1049      1 ifconfig CALL  __sigprocmask14(3,0x7fea5fd8,0)
  1049      1 ifconfig RET   __sigprocmask14 0
  1049      1 ifconfig PSIG  SIGILL SIG_DFL: code=ILL_ILLOPC, addr=0x5e7dbe68, trap=-519880546)
  1049      1 ifconfig NAMI  "ifconfig.core"

References:
- Anyone seeing problems with ifconfig(8) on the RPI with sources from January 5, 2017?
  - From: Brian Buhrow

Prev by Date: Anyone seeing problems with ifconfig(8) on the RPI with sources from January 5, 2017?
Next by Date: Re: Status of RPi 3 (b) ?
Previous by Thread: Anyone seeing problems with ifconfig(8) on the RPI with sources from January 5, 2017?
Indexes:

Home | Main Index | Thread Index | Old Index