don't know, we were using stunnel 4.52 and openssl 1.0.0.
the goal is to use stunnel 5.0.

right now i'm at the point, even if i move to stunnel 4.53, it starts crashing even without any arguments.
it should just print the help message, has nothing to do with openssl.

thanks for your reply !


CC: stunnel-users@stunnel.org
From: delaage.pierre@free.fr
Subject: Re: [stunnel-users] core dump when running stunnel on Arm based board
Date: Sun, 16 Dec 2012 12:08:09 +0100
To: ningji@hotmail.com

Hi, just a question : do you have an openssl lib matching your target platform ?with proper include files and libs accessible at compile time and run time ?
Pierre

Le 16 déc. 2012 à 04:24, ning ji <ningji@hotmail.com> a écrit :

actually problem starts from 4.53.

1. build and run 4.52 is fine
2. 4.53 crashes
3. setup gdb, as long as i connect to target, it says cannot access memory 0.
    after i set breakpoint at main() in stunnel.c, it get seg fault signal when i hit "continue" in gdb.

panic ...


From: ningji@hotmail.com
To: stunnel-users@stunnel.org
Date: Sat, 15 Dec 2012 15:43:09 +0000
Subject: [stunnel-users] core dump when running stunnel on Arm based board

Hi everyone, i'm new to this.

got a task to update stunnel from 4.52 to 5.00b1.

1. ./configure --host arm-none-linux-gnueabi --target   arm-none-linux-gnueabi --prefix= 
     i compared the makefile with the one in our 4.52 code base, same.

2. build with
     make -C stunnel CROSS_COMPILE=arm-none-linux-gnueabi- ARCH=arm

3. scp to ARM board, run without arugments, core dump.
    (the line number might be different as i was putting printfs. but as long as it enters parse_commandline, it crashes)

    [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 !

_______________________________________________ stunnel-users mailing list stunnel-users@stunnel.org https://www.stunnel.org/cgi-bin/mailman/listinfo/stunnel-users
_______________________________________________
stunnel-users mailing list
stunnel-users@stunnel.org
https://www.stunnel.org/cgi-bin/mailman/listinfo/stunnel-users