[Olsr-dev] SIGSEGV on G1/android
Sascha Alexander Jopen
Wed Oct 14 19:18:34 CEST 2009
i tried your precompiled binary and it works flawlessly. I could test
olsrd in a small adhoc network with 5 nodes.
But my self compiled binaries crash every time. I'm not sure how i can
provide a backtrace to you. I can run debian on the G1, so i have gdb
available, but then my binary won't load, because of different linkers
and even the different libc. Without debian, however, i have no gdb to
fetch a backtrace. Maybe i can find precompiled static gdb binaries, but
that may be problematic, too.
What did you mean by disabling setbuf(). Maybe this could work.
Attached is a log of my last build, where you can see the warnings.
Currently i'm not sure, what to do next.
Sven-Ola Tuecke schrieb:
> (last mail was from my mobile phone, kinda short for this reason)
> I do not have the segv you mention. Maybe different versions of the bionic
> libc on the HTC. Please try my binary first, just to make shure this is no
> cross-compile-toolchain issue:
> After unpacking, you'll notice an "ff" script. At least on the Samsung Galaxy,
> I needed some script wizardry to get the phone to join an IBSS Wifi, the
> reason for this script.
> // Sven-Ola
> Am Dienstag 13 Oktober 2009 19:29:11 schrieb Sascha Alexander Jopen:
>> i'm trying to build and run olsrd-0.5.6-r6 on my G1. Besides three
>> different compiler warnings on nearly all source files the binary can be
>> build successfully. But i can not run the application on the G1. It
>> crashes with SIGSEGV immediately.
>> I have attached a strace of running olsrd on the G1. The strace
>> suggests, that the failure occurs at process initialization, just before
>> the actual olsrd code is run. I'm not sure, if this is a problem of the
>> runtime environment on my phone or if it is a compile time issue. I
>> don't know how i could debug the application when running on the G1.
>> Maybe someone could help me get olsrd running on android.
>> A precompiled binary which is known to work would be nice. So i could
>> check if it's the phone, which is causing the troubles.
>> Thanks in advance,
>> Sascha Jopen
More information about the Olsr-dev