On 04/04/2022 10:10, Chris Johns wrote:
> Hi
>
> I'm trying to track down an issue with ssl in python, which used OpenSSL
> 1.1. To try to reduce the number of moving parts, I've managed to narrow
> it down to a smaller test.
>
> The setup is .. the C code below (which runs fine on linux) has been
> compiled on RISC OS (native) with GCC10 (buult from the auto builder).
> LibSSL (1.1.0) is the one I built with the auto-builder, but I had to
> tweak it to use the 1.1.0n (rather than m) sources and I built it for
> armv6z (IIRC) instaad of armv3.
[snip]
> Anyone any ideas?
If *showregs gives a valid value for r15, and that is within a library,
then
*somaddress pc
should tell you which library and where. You can then use the library
offset given together with the output from
*nm -Dn <library>
to determine which function the crash occurs in. Finally, a few
printf's in the offending function to narrow it down even further.
That's what I usually do.
Lee.
_______________________________________________
GCCSDK mailing list gcc@gccsdk.riscos.info
Bugzilla: http://www.riscos.info/bugzilla/index.cgi
List Info: http://www.riscos.info/mailman/listinfo/gcc
Main Page: http://www.riscos.info/index.php/GCCSDK
No comments:
Post a Comment