Hi!
I tested starting ser with all common and ser's modules - in arbitrary order. Of course this failed, nevertheless ser should not crash:
root@flunder:/# ser loading modules under /usr/local/lib/ser/modules:/usr/local/lib/ser/modules_s ERROR: bad config file (29 errors) Segmentation fault (core dumped)
backtrace:
Core was generated by `ser'. Program terminated with signal 11, Segmentation fault. [New process 25251] #0 0xb6fa08f4 in tree_get () at tree.c:290 290 tree = *shared_tree; (gdb) bt #0 0xb6fa08f4 in tree_get () at tree.c:290 #1 0xb6fa0a34 in tree_close () at tree.c:337 #2 0xb6f9f428 in mod_destroy () at prefix_route.c:222 #3 0x080ea281 in destroy_modules () at sr_module.c:631 #4 0x080896f8 in cleanup (show_status=0) at main.c:501 #5 0x0808a114 in shutdown_children (sig=15, show_status=0) at main.c:621 #6 0x0808f45b in main (argc=1, argv=0xbfffa134) at main.c:2116
regards Klaus
On Jul 03, 2009 at 15:45, Klaus Darilion klaus.mailinglists@pernau.at wrote:
Hi!
I tested starting ser with all common and ser's modules - in arbitrary order. Of course this failed, nevertheless ser should not crash:
root@flunder:/# ser loading modules under /usr/local/lib/ser/modules:/usr/local/lib/ser/modules_s ERROR: bad config file (29 errors) Segmentation fault (core dumped)
Thanks, it was the prefix_route module which did not take into the account the possibility of mod_destroy being called without mod_init being called first. It should be fixed now (7fc0ed0).
Andrei
-
Andrei Pelinescu-Onciul -
Klaus Darilion