[Olsr-dev] Master tree: all routers segmentation fault when 1 node leaves the network.
Henning Rogge
(spam-protected)
Fri Jun 11 13:04:39 CEST 2010
On Tue June 8 2010 23:19:56 ZioPRoTo (Saverio Proto) wrote:
> Hello,
>
> I'm working on the development tree and I found a bug that I cannot
> exactly reproduce.
>
> I'm running a network in my virtual environment with 7 routers, and
> when 1 (any) of the routers stops, all the other 6 nodes will have a
> segmentation fault after about 30 seconds.
>
> From this file it is easy to understand the topology, where every OLSR
> router has some interfaces attached to some collision domain:
> https://svn.ninux.org/ninuxdeveloping/browser/obamp-netkitlab/lab.conf
>
> I'm running OLSR into gdb, at the end of the email a couple of
> different backtraces I found. Once I also had a segmentation fault on
> ip4cmp function but I did not cut and paste and I was not able to
> reproduce it.
>
> I will fill a bug on tracker soon... first I wanted to understand if
> it was more reproducible...
I really hate the tc_set...
Can you enter a bug report and test the patch attached to this mail ? It
should prevent the segfault racecondition in the tc_set.
Henning
--
Diplom-Informatiker Henning Rogge , Fraunhofer-Institut für
Kommunikation, Informationsverarbeitung und Ergonomie FKIE
Kommunikationssysteme (KOM)
Neuenahrer Straße 20, 53343 Wachtberg, Germany
Telefon +49 228 9435-961, Fax +49 228 9435 685
mailto:(spam-protected) http://www.fkie.fraunhofer.de
GPG: E1C6 0914 490B 3909 D944 F80D 4487 C67C 55EC CFE0
-------------- next part --------------
A non-text attachment was scrubbed...
Name: tc.patch
Type: text/x-patch
Size: 28838 bytes
Desc: not available
URL: <http://lists.olsr.org/pipermail/olsr-dev/attachments/20100611/aeb9d665/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.olsr.org/pipermail/olsr-dev/attachments/20100611/aeb9d665/attachment.sig>
More information about the Olsr-dev
mailing list