[Olsr-dev] Hello Generation

[Sven-Ola Tuecke]

Hey,

airton's not very talkative. He says:

- segfault.
- ipk?
- olsrd-0.5.6-r8.
- selfcompiled.

Not enough to help. IPK packages are used with OpenWrt Whiterussian and maybe 
for some handheld devices. So no gdb nor valgrind. May need to narrow down by 
while(segfault) do;add printf to code, compile, install on device, run;done

// Sven-Ola

Am Dienstag 23 März 2010 16:43:29 schrieb Airton Ishimori:
> I compiled olsrd-0.5.6.r-8. The olsrd -v or olsrd -h command with parameter
> -v or -h not exist. The output is
>
> Parsing file: "/etc/olsrd.conf"
> An error occured somwhere between your keyboard and your chair!
> usage: olsrd [-f <configfile>] [ -i interface1 interface2 ... ]
>   [-d <debug_level>] [-ipv6] [-multi <IPv6 multicast address>]
>   [-lql <LQ level>] [-lqw <LQ winsize>] [-lqnt <nat threshold>]
>   [-bcast <broadcastaddr>] [-ipc] [-dispin] [-dispout] [-delgw]
>   [-hint <hello interval (secs)>] [-tcint <tc interval (secs)>]
>   [-midint <mid interval (secs)>] [-hnaint <hna interval (secs)>]
>   [-T <Polling Rate (secs)>] [-nofork] [-hemu <ip_address>]
>   [-lql <LQ level>] [-lqa <LQ aging factor>]
> Terminated
>
> On Tue, Mar 23, 2010 at 12:35, Henning Rogge <(spam-protected)> wrote:
> > Am Dienstag 23 März 2010 16:26:00 schrieb Airton Ishimori:
> > > The valgrind program is it in wich ipk package??
> >
> > okay, if you are working on OpenWRT you wont find valgrind (because it
> > does not work on Arm/Mips architecture).
> >
> > Did you compile OLSRd yourself ?
> >
> > What does OLSRd outputs if your call
> >
> > "olsrd -v" or "olsrd -h" ?
> >
> > Henning
> >
> > > On Tue, Mar 23, 2010 at 11:58, Henning Rogge <(spam-protected)>
> >
> > wrote:
> > > > Am Dienstag 23 März 2010 15:52:14 schrieb Airton Ishimori:
> > > > > Hey,
> > > > >
> > > > > My debug with olsrd (I used olsrd -d 9):
> > > > >
> > > > > TIMER: fire Hello Generation timer 0x10010858, ctx 0x1000bdf8, at
> > > >
> > > > clocktick
> > > >
> > > > > 1730 (01:37:34.050180)
> > > > > Segmentation fault
> > > > >
> > > > > What happened??
> > > >
> > > > OLSRd segfaulted ;)
> > > >
> > > > Okay, let's get some more data.
> > > >
> > > > 1. What version of OLSRd are you using ?
> > > > 2. can you run OLSRd with valgrind to track the exact code part where
> >
> > the
> >
> > > > segfault happend ?
> > > > (install valgrind, then run "valgrind olsrd -d 9" and wait for the
> >
> > crash,
> >
> > > > you
> > > > should get some information where the programm crashed)
> > > >
> > > > Henning Rogge