segmentation fault as soon as entering 1 function in the arm processor board

Hi everyone,

i'm lost on this one, can someone give me some hints ?

1. downloaded latest stunnel package from web
2. build in the host linux and runs fine
3. build for arm target (am using the same settings from before,
my task is to upgrade to latest stunnel)
4. builds ok, when run in arm board, seg fault.
5. from gdb core,

[New LWP 867]
Cannot access memory at address 0x70797263
(gdb) bt
#0 parse_commandline (name=0xbefdce29 "/opt/ultra/config/stunnel.conf",
parameter=0xbefdce48 "-version") at options.c:1940
#1 0x0003ba04 in main_configure (
arg1=0xbefdce29 "/opt/ultra/config/stunnel.conf",
arg2=0xbefdce48 "-version") at stunnel.c:199
#2 0x0003bd44 in main_unix (argv=<optimized out>, argc=<optimized out>)
at stunnel.c:135
#3 main (argc=3, argv=0xbefdcd24) at stunnel.c:110


my question is, it crashed when just entering parse_commandline( ),
the 2 arguments look fine to me.
How could this happen ?

Many thanks !

I know zero about ARM, so forgive me if I'm wildly off track here but ...

That sure looks like a calling convention error. Each architecture has rules on how parameters are passed (on the stack or in which registers, etc.). But there are compiler options and various incantations in the source code that can select alternate rules for passing parameters.

The functions seems to have been compiled with different rules for how parameters are passed than the caller was compiled with.

My best estimate is that the caller has some text on its stack and the called function looks in that place on the caller's stack to find its a parameter (which is a pointer to text) so it ends up trying to use text as if it were a pointer to text.

If I'm on the right track at all, then gdb is in agreement with the caller regarding the way parameters are passed.