| |
PE1RRR > BPQ 29.04.20 20:19l 135 Lines 3838 Bytes #999 (0) @ WW
BID : 8726_PE1RRR
Read: GAST
Subj: Re: Compiling LinBPQ Beta on 64bit systems
Path: DB0FFL<OE2XZR<DB0FHN<DB0RBS<DB0ERF<OK0NAG<OK0NBR<SR1BSZ<EA2RCF<I0OJJ<
GB7CIP<PE1RRR
Sent: 200429/1806Z 8726@PE1RRR.NLD.EURO LinBPQ6.0.20
Hi
If you want to be useful, please provide a stack trace using gdb and postin=
g it to the groups.io or to G8BPQ@G8BPQ.GBR.EURO
gdb -p `pidof linbpq`
input commands:
continue
After segfault:
backtrace
73s
Red
On Wed, 29 Apr 20 13:55:00 Z
I0OJJ wrote:
> R:200429/1400Z @:CX2SA.SAL.URY.SOAM #:30171 [Salto] FBB7.00e $:076C0_I0OJJ
> R:200429/1357Z @:IR4U.IEMR.ITA.EU #:14002 [Cesena] $:076C0_I0OJJ
> R:200429/1357z @:IZ3LSV.IVEN.ITA.EU $:076C0_I0OJJ
> R:200429/1454z @:I3XTY.TV.IVEN.ITA.EU $:076c0_I0OJJ
> R:200429/1355z @:I0OJJ.ITA.EU [Rome] #:8634 $:076c0_I0OJJ
>=20
> Hi,
>=20
> On 4/29/20 12:16 PM, pe1rrr@pe1rrr.nld.euro wrote:
> > R:200429/1020z @:I0OJJ.ITA.EU $:8702_PE1RRR
> > R:200429/1017Z @:GB7CIP.#32.GBR.EURO #:54090 [Caterham Surrey GBR]
> > R:200429/1016Z 8702@PE1RRR.NLD.EURO LinBPQ6.0.20
> >=20
> >=20
> > Hi folks
> >=20
> > While a build of the sources on 64bit linux WILL work, will RUN, it wil=
l get a lot of things very wrong and cause serious data
> > integrity issues. You MUST compile the sources with 32bit libraries, he=
re are my findings for doing that on a fresh Debian 10 6
> > 4bit system. A way to see a 64bit build failing spectacularly is by run=
ning 'nrr' from that host to any neighbor and watch the
> > fireworks occur in the traffic monitor as a netrom death spiral occurs =
(but still doesn't crash!).
>=20
>=20
> while it is superfluous to say that almost the whole
> packet-radio packages are created and run on 32-bit
> platforms there are other incompatibility remained
> nowadays in linbpq program.
>=20
> > Here's the procedure I created below for working with the CommonSources=
..zip:
>=20
>=20
> About the compiling: the results here remain the following,
> namely since years I get 'Segmentation fault' every time.
>=20
> ----------
> bash-4.3# rc.linbpq
> G8BPQ AX25 Packet Switch System Version 6.0.20.1 April 2020
> Copyright =A9 2001-2020 John Wiseman G8BPQ
> Current Directory is /linbpq
>=20
> Configuration file Preprocessor.
> Using Configuration file /linbpq/bpq32.cfg
> Conversion (probably) successful
>=20
> PORTS 0x81b5da0 LINKS 0x81b95f0 DESTS 0x81bdf60 ROUTES 0x81c5940 L4=20
> 0x81c6570 BUFFERS 0x81cdb18
>=20
> Initialising Port 01 AXIP
> Initialising Port 02 Telnet Server
> Initialising Port 03 ASYNC /dev/ttyp1 Chan A
> Initialising Port 04 Loopback
> IP Using eth0
> Successfully connected to TAP interface LinBPQTAP
> TAP brought up
> TAP MTU set to 256
> Route to 44/8 added via LinBPQTAP
> Net44 Tunnel opened on PCAP device
> IP Support Enabled
> Starting Mail
> Config File is /linbpq/linmail.cfg
> Config Processed
> Config File Line -1218084247 - (null)
> /usr/local/bin/rc.linbpq: line 13: 4318 Segmentation fault ./linbpq
> bash-4.3#
> -------------
>=20
> While the released compile of 'linbpq' is stable (at least
> without stressing the system), it remains to be handicapped
> on collect the 'encap' address; the *wrong* results obtained
> here, follows:
>=20
> <SNIP>
> ----
> ENCAPMAC 00:00:00:00:00:00
> 134.209.164.184/32 134.209.164.184 E 0 0
> 139.99.125.191/32 139.99.125.191 E 0 0
> 141.98.80.204/32 141.98.80.204 E 0 0
> 142.93.183.128/32 142.93.183.128 E 0 0
> 153.178.140.223/32 153.178.140.223 E 0 0
> 158.69.251.161/32 158.69.251.161 E 0 0
> 159.65.80.142/32 159.65.80.142 E 0 0
> 162.243.138.54/32 162.243.138.54 E 0 0
> 162.243.139.246/32 162.243.139.246 E 0 0
> 162.243.143.64/32 162.243.143.64 E 0 0
> 164.68.112.178/32 164.68.112.178 E 0 0
> 165.22.187.76/32 165.22.187.76 E 0 0
> 167.99.162.154/32 167.99.162.154 E 0 0
> ...
> ...
> <SNIP>
>=20
> No way to be understood by the *good*
> G8BPQ author, but that it's all :)
>=20
> --=20
> 73 and ciao, gustavo i0ojj/ir0aab/ir0eq
> SICD project Rome Italy
> Quidquid latine dictum sit, altum videtur
>=20
>=20
>=20
--=20
Red <pe1rrr@pe1rrr.ampr.org>
Lese vorherige Mail | Lese naechste Mail
| |
