[Olsr-dev] Hello Generation

[Airton Ishimori]

No, the segfault is for all debug level...


On Tue, Mar 23, 2010 at 13:06, Markus Kittenberger <
(spam-protected)> wrote:

> i think the best emthod to debug something on openwrt is gdbserver
>
> but to get it working is maybe a bit too much of overhead for just finding
> a segfault (which maybe is only caused by the debug output) (this depends if
> your a familiar with gdb)
>
> does your olsrd segfault only if u do -d 9 ?
>
> or did it already segfault before you used -d 9?
>
> or does it crash anyway
>
> regardsa Markus
>
> On Tue, Mar 23, 2010 at 4:26 PM, Airton Ishimori <(spam-protected)>wrote:
>
>> The valgrind program is it in wich ipk package??
>>
>>
>>
>> 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
>>>
>>
>>
>> --
>> Olsr-dev mailing list
>> (spam-protected)
>> http://lists.olsr.org/mailman/listinfo/olsr-dev
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.olsr.org/pipermail/olsr-dev/attachments/20100323/3909d18a/attachment.html>