[Olsr-users] Setting Debug Mode greater than 0 causes olsrd to crash at startup

[Harald Sighart]

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







2013/12/5 Henning Rogge <(spam-protected)>

> On 12/03/2013 05:45 PM, Harald Sighart wrote:
> > 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?
>
> 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
> mailto:(spam-protected) http://www.fkie.fraunhofer.de
>
>
> --
> Olsr-users mailing list
> (spam-protected)
> https://lists.olsr.org/mailman/listinfo/olsr-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.olsr.org/pipermail/olsr-users/attachments/20131209/66ca87d3/attachment.html>