Re: Segfault/Crash
By: Digital Man to KK4QBN on Tue Nov 21 2017 10:06 pm
> Re: Segfault/Crash
> By: KK4QBN to Digital Man on Tue Nov 21 2017 10:04 pm
>
> > Hey Rob,
>
> > The Segfault, Crashing I messaged you about a few days ago has went away
> > when I took two DNSBL options out of sbbs.ini:
>
> > DNSBL_SPAMHASH | DNSBL_THROTTLE
>
> > Took those out and have'nt had any type of segfault in 2 days now,
> > running either in daemon or terminal mode.
>
> Unfortunately, that doesn't really help. Can you re-enable the configuration
> you had to reproduce the problem and provide a backtrace from gdb? That'd
> help. :-)
>
> > but have a new one on you.
>
> > getting this when first initilizing when starting up fresh, not
> > recycling.
>
> > 11/21 21:49:21 term Synchronet Terminal Server Version 3.17 Revision A
> > 11/21 21:49:21 term Compiled Nov 12 2017 18:16:59 with GCC 4.9.2
> > 11/21 21:49:21 term Initializing on Tue Nov 21 21:49:21 2017 with
> > options: 183a 11/21 21:49:21 term Loading configuration files from
> > /sbbs/ctrl/
> > 11/21 21:49:21 term Configured time zone (AST, 0x40F0, offset: -240) does
> > not match system-local time zone offset: -300
>
>
> > Have made no time changes in my system, I'm set to EDT.
>
> Synchronet seems to think you have SCFG->System->Local Time Zone set to
> "AST". You want to double-check that?
Okay, but wouldn't it be EST (standard time) now?
But 0x40f0 is definitely "AST" (from smbdefs.h):
#define AST 0x40F0 /* Atlantic (-04:00) */
#define EDT 0xC12C /* Eastern (-04:00) */
They're both -240 (-4:00) from UTC, but daylight saving time is not in effect
right now (here in the U.S. at least), so perhaps just changing that to EDT
will fix it (or enable Auto-DST).
digital man
This Is Spinal Tap quote #4:
David St. Hubbins: He died in a bizarre gardening accident...
Norco, CA WX: 81.7øF, 23.0% humidity, 1 mph WSW wind, 0.00 inches rain/24hrs
--- SBBSecho 3.03-Win32
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
|