Re: head -r333974 fix-to-the-build exposes another breaks-the-build problem in top (at least for gcc based builds)

2018-05-22 Thread Eitan Adler
On 21 May 2018 at 18:06, Mark Millard wrote: > On 2018-May-21, at 5:46 PM, Mark Millard wrote: > I should have been explicit that the material is from > ci.freebsd.org . Your email seems to always be marked as spam by my MUA even though SPF, DKIM, and DMARC pass.

Re: head -r333974 fix-to-the-build exposes another breaks-the-build problem in top (at least for gcc based builds)

2018-05-21 Thread Mark Millard
On 2018-May-21, at 5:46 PM, Mark Millard wrote: > FreeBSD-head-amd64-gcc (based on a more modern gcc) reports a > more explicit error for -r333974 and later: > > --- all_subdir_usr.bin --- > /workspace/src/usr.bin/top/commands.c:132:1: error: function declaration > isn't a prototype

head -r333974 fix-to-the-build exposes another breaks-the-build problem in top (at least for gcc based builds)

2018-05-21 Thread Mark Millard
FreeBSD-head-amd64-gcc (based on a more modern gcc) reports a more explicit error for -r333974 and later: --- all_subdir_usr.bin --- /workspace/src/usr.bin/top/commands.c:132:1: error: function declaration isn't a prototype [-Werror=strict-prototypes] scanint(str, intp) ^~~ The older gcc

Re: problem with top

2012-07-02 Thread John Baldwin
On Saturday, June 30, 2012 7:54:58 pm Erich Dollansky wrote: Hi, On Sunday, July 01, 2012 06:51:41 AM AN wrote: FreeBSD FBSD10 10.0-CURRENT FreeBSD 10.0-CURRENT #23 r237852: Sat Jun 30 18:45:27 EDT 2012 root@FBSD10:/usr/obj/usr/src/sys/MYKERNEL amd64 After a recent upgrade, I am

problem with top

2012-06-30 Thread AN
FreeBSD FBSD10 10.0-CURRENT FreeBSD 10.0-CURRENT #23 r237852: Sat Jun 30 18:45:27 EDT 2012 root@FBSD10:/usr/obj/usr/src/sys/MYKERNEL amd64 After a recent upgrade, I am seeing a formatting issue with top. top -SPH -s 1: last pid: 26011; load averages: 3.61, 2.80, 1.56

Re: problem with top

2012-06-30 Thread Erich Dollansky
Hi, On Sunday, July 01, 2012 06:51:41 AM AN wrote: FreeBSD FBSD10 10.0-CURRENT FreeBSD 10.0-CURRENT #23 r237852: Sat Jun 30 18:45:27 EDT 2012 root@FBSD10:/usr/obj/usr/src/sys/MYKERNEL amd64 After a recent upgrade, I am seeing a formatting issue with top. top -SPH -s 1: last pid:

Re: Problem with top on current ?

1999-02-06 Thread Brian Feldman
On Fri, 5 Feb 1999, Matthew Dillon wrote: : :Ahhh...not sure what you mean here... : :On 06-Feb-99 Brian Feldman wrote: : On Fri, 5 Feb 1999, William Woods wrote: : Floating point exception :... : : Try kvm_mkdb yet? : :-- :E-Mail: William

Problem with top on current ?

1999-02-05 Thread William Woods
Running 4.0 -Current build as of a few miniutesd ago, I go to run top and I get. top: cannot read *swapblist: kvm_read: Bad address top: cannot read blmeta_t: kvm_read: Bad address Floating point exception -- E-Mail: William Woods wwo...@cybcon.com

Re: Problem with top on current ?

1999-02-05 Thread Brian Feldman
On Fri, 5 Feb 1999, William Woods wrote: Running 4.0 -Current build as of a few miniutesd ago, I go to run top and I get. top: cannot read *swapblist: kvm_read: Bad address top: cannot read blmeta_t: kvm_read: Bad address Floating point exception Try kvm_mkdb yet?

Re: Problem with top on current ?

1999-02-05 Thread William Woods
Ahhh...not sure what you mean here... On 06-Feb-99 Brian Feldman wrote: On Fri, 5 Feb 1999, William Woods wrote: Running 4.0 -Current build as of a few miniutesd ago, I go to run top and I get. top: cannot read *swapblist: kvm_read: Bad address top: cannot read blmeta_t:

Re: Problem with top on current ?

1999-02-05 Thread Matthew Dillon
: :Ahhh...not sure what you mean here... : :On 06-Feb-99 Brian Feldman wrote: : On Fri, 5 Feb 1999, William Woods wrote: : Floating point exception :... : : Try kvm_mkdb yet? : :-- :E-Mail: William Woods wwo...@cybcon.com Try this: cd

Re: Problem with top on current ?

1999-02-05 Thread William Woods
Just tried that, same error. On 06-Feb-99 Matthew Dillon wrote: : :Ahhh...not sure what you mean here... : :On 06-Feb-99 Brian Feldman wrote: : On Fri, 5 Feb 1999, William Woods wrote: : Floating point exception :... : : Try kvm_mkdb yet? : :--