Yo Hal!
On Tue, 30 May 2017 23:02:50 -0700
Hal Murray via devel wrote:
> I get this when trying to run ntpd.
>
> Every time I see this, I remember "Oh, yeah. It doesn't work here."
> I just want to make sure I'm not missing something simple.
gdb stack trace often fails if compiled with -Ox wh
Yo Hal!
On Tue, 30 May 2017 23:12:40 -0700
Hal Murray wrote:
> Gary said:
> > There was never a way to decode the addresses beyond that. Is that
> > any use? Any way to improve it so it has value?
>
> > #5 0x556b8bed9299 in ??
>
> I assume those are PCs.
Yes.
> Is there a way to get gd
Gary said:
> There was never a way to decode the addresses beyond that. Is that any use?
> Any way to improve it so it has value?
Thanks.
> #0 0x556b8bf1d76f in ??
> #1 0x556b8bf1d65a in ??
> #2 0x556b8beecf8f in ??
> #3 0x556b8beed060 in ??
> #4 0x7f81ca395720 in ??
> #5 0x556b8bed9299 in ??
I get this when trying to run ntpd.
Every time I see this, I remember "Oh, yeah. It doesn't work here." I just
want to make sure I'm not missing something simple.
Program received signal SIGILL, Illegal instruction.
_armv7_tick () at armv4cpuid.S:17
17 armv4cpuid.S: No such file or direc
Yo Hal!
By jamming a number of #defines the hard way, I get libisc backtrace
to do what it is supposed to do:
../../ntpd/ntpd.c:930: REQUIRE(1 == 2) failed, back trace
#0 0x556b8bf1d76f in ??
#1 0x556b8bf1d65a in ??
#2 0x556b8beecf8f in ??
#3 0x556b8beed060 in ??
#4 0x7f81ca395720 in ??
#5 0x556b
Yo Hal!
On Tue, 30 May 2017 16:44:48 -0700
Hal Murray wrote:
> gdb doesn't work when ntpd is started automatically at boot time.
OK.
> strace solved that one.
Yes, we keep coming back to strace.
> There is another problem in this area. That's translating a stack
> trace in the middle of lib
> Every instance I've seen has the logging code enclosed in an #ifdef block
> for the debug compilation switch, whether directly where it is used, of
> inside of a macro. It would appear that someone began to replace the
> explicit if debugs with macros, but never completed it for unknown reason
> I'll be seeing if even that works, and if it works, how it compares to gdb
> backtrace.
gdb doesn't work when ntpd is started automatically at boot time. That's
interesting because, at least on my laptop, wifi doesn't get started until
after ntpd is running. That tested a code path I never
Gary E. Miller via devel :
> Yo Ian!
>
> On Tue, 30 May 2017 16:34:07 -0500
> Ian Bruene via devel wrote:
>
> > Every instance I've seen has the logging code enclosed in an #ifdef
> > block for the debug compilation switch, whether directly where it is
> > used, of inside of a macro. It would
Yo Ian!
On Tue, 30 May 2017 16:34:07 -0500
Ian Bruene via devel wrote:
> Every instance I've seen has the logging code enclosed in an #ifdef
> block for the debug compilation switch, whether directly where it is
> used, of inside of a macro. It would appear that someone began to
> replace the
Yo Mark!
On Tue, 30 May 2017 21:31:59 +
Mark Atwood wrote:
> I remain a fan of ripping out unused and useless code.
Good. First I'll be sure it is truly useless. So far iI see it
only tries to work on x86 and i386 cpus, with a srtong preference
for gcc.
I'll be seeing if even that works,
At ESRs request I've trawled through the C sources to see how debug
logging is handled. First, by way of summary let me present you with a
couple bits of code:
# define DPRINTF(lvl, arg)\
do { \
if (debug >= (lvl))\
mpr
I remain a fan of ripping out unused and useless code.
As you remove stuff, do please keep each conceptual chunk of removal in
it's own well defined git commit.
..m
On Fri, May 26, 2017 at 9:12 PM Gary E. Miller via devel
wrote:
> Yo All!
>
> I see a lot of libisc code that I'm not sure NTPsec
Kurt Roeckx writes:
> Adding random (white) noise to a measurement is done to improve the
> resolution after averaging, it's ussually in combination with
> oversampling. Adding this white noise is done in the analog signal,
> before you convert it to digital.
The other use of that approach is to d
14 matches
Mail list logo
