Setting Debug Mode greater than 0 causes olsrd to crash at startup

Discussion:

Harald Sighart

2013-12-03 16:45:10 UTC

Hello!

First of all thanks for providing that great piece of Software!

I tried to get into olsr during the last days and had my first successes.
But when Setting the debug Level in the olsr.conf to somethign else than 0
the demon crashes at startup.

My Platform is Windows 7.
I am using olsrd 0.6.6 built with MinGW.

The last lines I see before the demon stops is:

TIMER: jitter 5% rel_time 1000ms to 993ms
SPF: insert candidate 192.168.243.10, cost 0.000
SPF: exploring node 192.168.243.10, cost 0.000
SPF: delete candidate 192.168.243.10, cost 0.000
SPF: append path 192.168.243.10, cost 0.000, via -
--- 17:40:47.631000 -------------------------------------------------
DIJKSTRA
Updating kernel routes...
--- 17:40:47.641000 ------------------------------------------------- MID

--- 17:40:47.641000 ----------------------------------------------------
LINKS
IP address hyst LQ ETX

Windows just says (sorry it is german):

*Problemsignatur: *

Problemereignisname: APPCRASH

Anwendungsname: olsrd.exe

I have started olsrd in a Windows command line that is run as Administrator.

Did anybody Encounter the same Problem and has a solution for it?

As I am new to olsr and to the list, I hope you forgive me if this question
has already been asked. I tried to read thorugh as much archives as
possible but I may have overlooked it.

Thanks,
Harald

Henning Rogge

2013-12-05 06:54:12 UTC

Permalink

Post by Harald Sighart
Hello!
First of all thanks for providing that great piece of Software!
I tried to get into olsr during the last days and had my first
successes. But when Setting the debug Level in the olsr.conf to
somethign else than 0 the demon crashes at startup.
My Platform is Windows 7.
I am using olsrd 0.6.6 built with MinGW.
TIMER: jitter 5% rel_time 1000ms to 993ms
SPF: insert candidate 192.168.243.10, cost 0.000
SPF: exploring node 192.168.243.10, cost 0.000
SPF: delete candidate 192.168.243.10, cost 0.000
SPF: append path 192.168.243.10, cost 0.000, via -
--- 17:40:47.631000 -------------------------------------------------
DIJKSTRA
Updating kernel routes...
--- 17:40:47.641000 ------------------------------------------------- MID
--- 17:40:47.641000 ----------------------------------------------------
LINKS
IP address hyst LQ ETX
*
*
Problemereignisname: APPCRASH
Anwendungsname: olsrd.exe
I have started olsrd in a Windows command line that is run as Administrator.
Did anybody Encounter the same Problem and has a solution for it?

--
Diplom-Informatiker Henning Rogge , Fraunhofer-Institut für
Kommunikation, Informationsverarbeitung und Ergonomie FKIE
Kommunikationssysteme (KOM)
Fraunhofer Straße 20, 53343 Wachtberg, Germany
Telefon +49 228 9435-961, Fax +49 228 9435 685
mailto:***@fkie.fraunhofer.de http://www.fkie.fraunhofer.de

Harald Sighart

2013-12-09 10:17:29 UTC

Permalink

I followed your advice and thats the result:

First, I am using MinGW

The Crash Location is in neighbor_table.c
after the following lines:

(void)*gettimeofday*(&now, NULL);

*nowtm* = *localtime*((time_t *)*&now.tv_sec*);

nowtm is still a nullpointer.

As anyway in other functions

olsr_wallclock_string()
is used to print the time in debug Outputs, I replaced the nowtm solution
with the

olsr_wallclock_string()

That works now.

Thanks,

Harald

Post by Harald Sighart

Administrator.

Post by Harald Sighart
Did anybody Encounter the same Problem and has a solution for it?

Before we find a solution we must find the problem...
What did you use to compile olsrd? Cygwin or MinGW?
Can you maybe install GDB (Gnu Debugger) and use it to pinpoint the
crash location?
Run "gdb --args olsrd -d 1" and then enter the "run" command. When GDB
displays the crash, enter "bt" (backtrace) and post the whole output here.
Henning Rogge
--
Diplom-Informatiker Henning Rogge , Fraunhofer-Institut für
Kommunikation, Informationsverarbeitung und Ergonomie FKIE
Kommunikationssysteme (KOM)
Fraunhofer Straße 20, 53343 Wachtberg, Germany
Telefon +49 228 9435-961, Fax +49 228 9435 685
--
Olsr-users mailing list
https://lists.olsr.org/mailman/listinfo/olsr-users

Ferry Huberts

2013-12-09 10:46:06 UTC

Permalink

I've pushed the fix for this issue onto the release-0.6.5, release-0.6.6
and master branches.

Thanks for reporting and investigating!

Post by Harald Sighart
First, I am using MinGW
The Crash Location is in neighbor_table.c
(void)_gettimeofday_(&now, NULL);
_nowtm_ = _localtime_((time_t *)_&now.tv_sec_);
nowtm is still a nullpointer.
As anyway in other functions
olsr_wallclock_string()
is used to print the time in debug Outputs, I replaced the nowtm
solution with the
olsr_wallclock_string()
That works now.
Thanks,
Harald

------------------------------------------------- MID

Post by Harald Sighart
--- 17:40:47.641000

----------------------------------------------------

Post by Harald Sighart
LINKS
IP address hyst LQ ETX
*
*
Problemereignisname: APPCRASH
Anwendungsname: olsrd.exe
I have started olsrd in a Windows command line that is run as

Administrator.

Post by Harald Sighart
Did anybody Encounter the same Problem and has a solution for it?

Before we find a solution we must find the problem...
What did you use to compile olsrd? Cygwin or MinGW?
Can you maybe install GDB (Gnu Debugger) and use it to pinpoint the
crash location?
Run "gdb --args olsrd -d 1" and then enter the "run" command. When GDB
displays the crash, enter "bt" (backtrace) and post the whole output here.
Henning Rogge
--
Diplom-Informatiker Henning Rogge , Fraunhofer-Institut für
Kommunikation, Informationsverarbeitung und Ergonomie FKIE
Kommunikationssysteme (KOM)
Fraunhofer Straße 20, 53343 Wachtberg, Germany
Telefon +49 228 9435-961 <tel:%2B49%20228%209435-961>, Fax +49 228
9435 685 <tel:%2B49%20228%209435%20685>
--
Olsr-users mailing list
https://lists.olsr.org/mailman/listinfo/olsr-users

--
Ferry Huberts
--
Olsr-users mailing list
Olsr-***@lists.olsr.org
https://lists.olsr.org/mailman/listinfo/olsr-users