Segmentation fault when starting G-WAN 3.12.26 32-bit on linux fc14

Question

I have a fc14 32 bit system with 2.6.35.13 custom compiled kernel. When I try to start G-wan I get a "Segmentation fault".I've made no changes, just downloaded and unpacked the files from g-wan site.

In the log file I have: "[Wed Dec 26 16:39:04 2012 GMT] Available network interfaces (16)" which is not true, on the machine i have around 1k interfaces mostly ppp interfaces.

I think the crash has something to do with detecting interfaces/ip addresses because in the log after the above line I have 16 lines with ip's belonging to the fc14 machine and after that about 1k lines with "0.0.0.0" or "random" ip addresses.

I ran gwan 3.3.7 64-bit on a fc16 with about the same number of interfaces and had no problem,well it still reported a wrong number of interfaces (16) but it did not crashed and in the log file i got only 16 lines with the ip addresses belonging to the fc16 machine.

Any ideas?

Thanks

Answer 1

I have around 1k interfaces mostly ppp interfaces

Only the first 16 will be listed as this information becomes irrelevant with more interfaces (the intent was to let users find why a listen attempt failed).

This is probably the long 1K list, many things have changed internally after the allocator was redesigned from scratch. Thank you for reporting the bug.

I also confirm the comment which says that the maintenance script crashes. Thanks for that.

Note that bandwidth shaping will be modified to avoid the newer Linux syscalls so the GLIBC 2.7 requirement will be waved.

...with a custom compiled kernel

As a general rule, check again on a standard system like Debian 6.x before asking a question: there is room enough for trouble with a known system - there's no need to add custom system components.

Thank you all for the tons(!) of emails received these two last days about the new release!

Answer 2

I had a similar "Segmentation fault" error; mine happens any time I go to 9+GB of RAM. Exact same machine at 8GB works fine, and 10GB doesn't even report an error, it just returns to the prompt.

Interesting behavior... Have you tried adjusting the amount of RAM to see what happens?

(running G-WAN 4.1.25 on Debian 6.x)