Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.sys.acorn.programmer > #5637

Re: A GnuTLS-Problem - problems fetchin emails using RISC OS

From Ron <gettingchoppy@gmail.com>
Newsgroups comp.sys.acorn.programmer
Subject Re: A GnuTLS-Problem - problems fetchin emails using RISC OS
Date 2018-12-20 09:10 +1300
Organization -
Message-ID <3f2c026957.beeb@-.-> (permalink)
References (3 earlier) <8e038e6757.beeb@-.-> <cd39ed6757.Eclipso@eclipso.at> <420ffc6757.beeb@-.-> <454f0a6857.beeb@-.-> <5600f66857.Eclipso@eclipso.at>

Show all headers | View raw


In message <5600f66857.Eclipso@eclipso.at>
          Alexander Ausserstorfer <alexander.ausserstorfer@eclipso.at> wrote:

> Ron <gettingchoppy@gmail.com> wrote:
> 
> > In message <420ffc6757.beeb@-.->
> >          Ron <gettingchoppy@gmail.com> wrote:
> >
> >> Will rebuild crypt nettle with new stable then build libgnutls28 again.
> >>
> >> Cheers RonM
> >>
> > OK I started from scratch and built all the libraries that are pulled in
> > by the libraries that are used in !POP3S
> > They are all from the current stable/stretch repository.
> > Should be at the same google drive link.
> >
> > It is worth trying a bigger wimpslot when unixlib aborts, newer stuff
> > often gets bigger.
> > Another idea would be to try the RiscPC using gcc without the optimise
> > flag.
> >
> > Let us know if compiling with those libraries improves things.
> > Note that the gnutls28 is renewed/rebuilt also.
> 
> Thank you very much for your help, support, work & time!
> 
> Here is what we got after starting the !Runimage file of
> 
> mail_applications -> armv3(all) -> pop3s-18th-dec.zip on a Risc PC 700
> with StrongARM:
> 
> | POP3S - E-Mail-fetcher with TLS for RISC OS
> | Developer Version 16. April 2016
> | GnuTLS version 3.5.8
> |
> | pop3.web.de
> |
> | Fatal signal received: Illegal Instruction
> |
> | Stack backtrace:
> |
> | Running thread 0x1fba98 (Main Thread)
> |   ( 1bfff30) pc:   181838 lr:   181ce4 sp:  1bfff34  __write_backtrace()
> |   ( 1bfffa0) pc:   181958 lr:   15c408 sp:  1bfffa4  __unixlib_raise_signal()
> |   ( 1bfffb0) pc:   15c30c lr:    f3e88 sp:  1bfe508  __h_cback()
> |
> |   Register dump at 01bfffb4:
> |
> |     a1:   2185db a2:   2185dc a3:  1bfe508 a4:        0
> |     v1:       1d v2:   2185db v3:   2185db v4:       1d
> |     v5: 1720a31a v6:   1f7808 sl:  1bfe208 fp:  1bfe570
> |     ip: f76da8e4 sp:  1bfe508 lr: 800f3e88 pc: 600f2e40
> |     Mode USR, flags set: nZCvif
> |
> |   000f2e2c : .@`å : e5604001 : STRB    R4,[R0,#-1]!
> |   000f2e30 : .0Sâ : e2533001 : SUBS    R3,R3,#1
> |   000f2e34 : ùÿÿ. : 1afffff9 : BNE     &000F2E20
> |   000f2e38 : ð.½è : e8bd0df0 : LDMIA   R13!,{R4-R8,R10,R11}
> |   000f2e3c : .ÿ/á : e12fff1e : BX      R14
> |   000f2e40 : .@qå : e5714001 : LDRB    R4,[R1,#-1]!
> |   000f2e44 : .Prå : e5725001 : LDRB    R5,[R2,#-1]!
> |   000f2e48 : .P%à : e0255004 : EOR     R5,R5,R4
> |   000f2e4c : .P`å : e5605001 : STRB    R5,[R0,#-1]!
> |
> |   ( 1bfe570) pc:    f3ddc lr:    b9594 sp:  1bfe574  nettle_salsa20r12_crypt()
> |   ( 1bfe5bc) pc:    b9528 lr:    b994c sp:  1bfe5c0  wrap_nettle_rnd_nonce.isra.0()
> |   ( 1bfe5cc) pc:    b9928 lr:    37be0 sp:  1bfe5d0  wrap_nettle_rnd()
> |   ( 1bfe5f0) pc:    37b6c lr:    14d7c sp:  1bfe5f4  gnutls_rnd()
> |   ( 1bfe684) pc:    14c20 lr:    1ae0c sp:  1bfe688  send_client_hello()
> |   ( 1bfe6b0) pc:    19c58 lr:     9668 sp:  1bfe6b4  gnutls_handshake()
> |   ( 1bfefec) pc:     9380 lr:   16a230 sp:  1bfeff0  main()
> |
> | *
> 
> I have now idea why this is happen and what's going on. It seems to run
> properly on my Raspberry Pi, though.
> 
> Alex
>
It still /appears/ to be a problem with nettle/gcrypt but I'm no good at
interpreting the machine code above that. Any advice from Druck?
Would running Armalyser on the libraries show any incompatible code?

The Dec18 !Runimage's are OK on my Iyonix also.
If you dont have a Strongarm machine at home it will be hard to try
different things. I might pull my one out of storage over the holidays.

There may be gcc options (suggestions anyone?) that could be tried. It
doesn't take long to compile each time, which is good.

It doesn't look like using different versions of the libraries has
helped, but at least the set at my google drive are all current stable
libs and not a mix of different eras.

The RiscPC does use a different memory system to RISC OS 5 but as long
as the wimpslot is big enough it shouldn't matter.
The !RunImage is over 2MB now.
I noticed if the wimpslot is close to the edge, it can fail when large
emails come through, just give it plenty (while testing anyway).

Ronald(NZ time)


Back to comp.sys.acorn.programmer | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

A GnuTLS-Problem - problems fetchin emails using RISC OS Alexander Ausserstorfer <alexander.ausserstorfer@eclipso.at> - 2018-12-16 16:25 +0100
  Re: A GnuTLS-Problem - problems fetchin emails using RISC OS Ron <gettingchoppy@gmail.com> - 2018-12-17 11:32 +1300
    Re: A GnuTLS-Problem - problems fetchin emails using RISC OS Alexander Ausserstorfer <alexander.ausserstorfer@eclipso.at> - 2018-12-17 00:25 +0100
      Re: A GnuTLS-Problem - problems fetchin emails using RISC OS Ron <gettingchoppy@gmail.com> - 2018-12-17 13:25 +1300
        Re: A GnuTLS-Problem - problems fetchin emails using RISC OS Alexander Ausserstorfer <alexander.ausserstorfer@eclipso.at> - 2018-12-17 18:45 +0100
          Re: A GnuTLS-Problem - problems fetchin emails using RISC OS Ron <gettingchoppy@gmail.com> - 2018-12-18 09:27 +1300
            Re: A GnuTLS-Problem - problems fetchin emails using RISC OS Ron <gettingchoppy@gmail.com> - 2018-12-18 12:03 +1300
              Re: A GnuTLS-Problem - problems fetchin emails using RISC OS Alexander Ausserstorfer <alexander.ausserstorfer@eclipso.at> - 2018-12-19 18:57 +0100
                Re: A GnuTLS-Problem - problems fetchin emails using RISC OS Ron <gettingchoppy@gmail.com> - 2018-12-20 09:10 +1300
                Re: A GnuTLS-Problem - problems fetchin emails using RISC OS druck <news@druck.org.uk> - 2018-12-20 08:11 +0000
                Re: A GnuTLS-Problem - problems fetchin emails using RISC OS news@sprow.co.uk - 2018-12-20 00:00 -0800
                Re: A GnuTLS-Problem - problems fetchin emails using RISC OS Alexander Ausserstorfer <alexander.ausserstorfer@eclipso.at> - 2018-12-20 19:03 +0100
              Re: A GnuTLS-Problem - problems fetchin emails using RISC OS David Higton <dave@davehigton.me.uk> - 2018-12-20 19:52 +0000
                Re: A GnuTLS-Problem - problems fetchin emails using RISC OS Ronald <gettingchoppy@gmail.com> - 2018-12-21 09:58 +1300
                Re: A GnuTLS-Problem - problems fetchin emails using RISC OS Ronald <gettingchoppy@gmail.com> - 2018-12-21 13:28 +1300
                Re: A GnuTLS-Problem - problems fetchin emails using RISC OS news@sprow.co.uk - 2018-12-21 00:39 -0800
                Re: A GnuTLS-Problem - problems fetchin emails using RISC OS Ronald <gettingchoppy@gmail.com> - 2018-12-21 23:29 +1300
                Re: A GnuTLS-Problem - problems fetchin emails using RISC OS Alexander Ausserstorfer <alexander.ausserstorfer@eclipso.at> - 2018-12-22 04:11 +0100
                Re: A GnuTLS-Problem - problems fetchin emails using RISC OS Ronald <gettingchoppy@gmail.com> - 2018-12-23 00:37 +1300
                Re: A GnuTLS-Problem - problems fetchin emails using RISC OS Alexander Ausserstorfer <alexander.ausserstorfer@eclipso.at> - 2018-12-22 04:16 +0100
                Re: A GnuTLS-Problem - problems fetchin emails using RISC OS Martin <News03@avisoft.f9.co.uk> - 2018-12-22 11:34 +0000
                Re: A GnuTLS-Problem - problems fetchin emails using RISC OS David Higton <dave@davehigton.me.uk> - 2018-12-22 17:16 +0000
                Re: A GnuTLS-Problem - problems fetchin emails using RISC OS Ronald <gettingchoppy@gmail.com> - 2018-12-23 09:54 +1300
                Re: A GnuTLS-Problem - problems fetchin emails using RISC OS David Higton <dave@davehigton.me.uk> - 2018-12-22 21:23 +0000
                Re: A GnuTLS-Problem - problems fetchin emails using RISC OS David Higton <dave@davehigton.me.uk> - 2018-12-23 20:12 +0000
                Re: A GnuTLS-Problem - problems fetchin emails using RISC OS druck <news@druck.org.uk> - 2018-12-22 21:59 +0000
                Re: A GnuTLS-Problem - problems fetchin emails using RISC OS Ronald <gettingchoppy@gmail.com> - 2018-12-23 11:50 +1300
                Re: A GnuTLS-Problem - problems fetchin emails using RISC OS Ronald <gettingchoppy@gmail.com> - 2018-12-23 14:35 +1300
                Re: A GnuTLS-Problem - problems fetchin emails using RISC OS druck <news@druck.org.uk> - 2018-12-23 14:22 +0000
                Re: A GnuTLS-Problem - problems fetchin emails using RISC OS news@sprow.co.uk - 2018-12-23 12:56 -0800
                Re: A GnuTLS-Problem - problems fetchin emails using RISC OS Matthew Phillips <spam2011m@yahoo.co.uk> - 2018-12-28 20:28 +0000
                Re: A GnuTLS-Problem - problems fetchin emails using RISC OS Ronald <gettingchoppy@gmail.com> - 2018-12-29 12:10 +1300

csiph-web