Open lampep opened 8 years ago
Can you recompile with debug symbols? Or is there something else related to your test environment that is preventing gdb from reading the executable?
On Wed, Apr 27, 2016 at 8:46 PM, Patrick Lampe notifications@github.com wrote:
As we described in #101 https://github.com/servalproject/serval-dna/issues/101 we ran some tests with serval.
Another test for serval is to start 100 nodes and bridge them together on a hub. In case of this test we realised serval crashes on some nodes. It's the same configuration that is working on other network topologies.
We have extracted the fatal messages from the log and attached them. If you need more information we're happy to send them to you. Any Ideas what causes this?
serval_hub_dump.txt https://github.com/servalproject/serval-dna/files/238510/serval_hub_dump.txt
— You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub https://github.com/servalproject/serval-dna/issues/102
We recompiled the binary with debug symbols. Here's the dump of the error: serval_fatals_dump.txt
Temporarily adding extra asserts to _ob_append_bytes() to help Lars get more detailed info. Can strip those out after Lars has reported the results. 382694464bd4f6d3722475ae9a78a480d5c407ed
Note that the crash from the first comment looks like the same one as #103. This second crash is different.
As we described in #101 we ran some tests with serval.
Another test for serval is to start 100 nodes and bridge them together on a hub. In case of this test we realised serval crashes on some nodes. It's the same configuration that is working on other network topologies.
We have extracted the fatal messages from the log and attached them. If you need more information we're happy to send them to you. Any Ideas what causes this?
serval_hub_dump.txt
Edit: we just realised our serval is built without a symbol table. If you need more details from the dump we could recompile serval.