Re: [fpc-pascal] Building trunk of today fails on Windows: Error: Invalid DLL C:\WINDOWS\system32\common.dll, invalid header size

2023-04-08 Thread Bo Berglund via fpc-pascal 
On Mon, 23 Aug 2021 23:01:39 +0200, Bart via fpc-devel
 wrote:

Replying here since my attempt at replying in the devel group failed...


>On Mon, Aug 23, 2021 at 8:04 PM Bart  wrote:
>
>> And, of course, the guide on how to remove this utility
>> (https://www.intel.com/content/www/us/en/support/articles/32459/processors/processor-utilities-and-programs.html)
>> do not apply.
>> No XtuService in "Apps and Features", no XtuService.exe. in any of the
>> suggested locations.
>
>Finally good news.
>
>In taskmanager I had to stop one process,then go to services, find
>xtu3service.exe, right-click, then "open services", find that service
>again (now called XTUOCDriverService) in the newly opened window,
>right-click, select properties, then set Startup type (? "Opstart
>type") to Disabled.
>
>After a reboot I was able to rename that common.dll to _common.dll,
>rebooted again.
>All this as administrator of course.
>
>Finally after all that I was able to build fpc for 32-bit.
>
>And now just hoping that with the nex Windows update it won't get
>re-installed again.

Bart, thanks for this description which I found now 19 months later!

I had trouble when installing the Win32 version of Lazarus/Fpc using fpcupdeluxe
(needed because I wanted a cross-compile tool for RaspberryPi on my Windows10
x64 box).

The install failed no matter what I did with an error message that was hard to
decode for me.

Now I have done the following as described above:

- Started Servicemanager on my Win10 workstation.

- Found the Intel service "XTUOCDriverService" and stopped it

- Then I also set the type to disabled.

- But I did *not* reboot, instead I renamed the common.dll in
C:\Windows\SysWOW64 to _common.dll, which was allowed now.

- Then I just started the fpcupdeluxe 32 bit exe and commanded it to install
3.2.2/Lazarus 2.2.6. And this time it succeeded!

- So when it was done I could tell fpcupdeluxe to install the cross-compiler for
arm-linux, which it also successfully completed.

The base install took 19m30s and the cross another 5 minutes when it fetched the
various source files from the Internet.

And the new cross-compiler actually works to build applications for RaspberryPi
on Widows10! :-)

And Win64 applications from this 32 bit install as a cross...


-- 
Bo Berglund
Developer in Sweden

___
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
https://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal

Re: [fpc-pascal] Building trunk

2018-12-01 Thread C Western 

On 30/11/2018 10:26, Cyrax wrote:

On 30/11/2018 12:23, Cyrax wrote:

On 30/11/2018 11:12, C Western wrote:

On 30/11/2018 04:23, Cyrax wrote:

On 30/11/2018 00:53, C Western wrote:

On 26/11/2018 22:46, - - wrote:
An additional note - it may well be a ld version issue. On Ubuntu 
the ld version is 2.30, but on Fedora ld reports 2.31.1-13.fc29. 
(Maybe I should have held off upgrading to Fedora 29...)


Colin
___
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal


Looking at this a little more I think the headers are simply not 
available to the program. Simply commenting out the INITTLS call 
allows the compiler to be built successfully. I note that 
multi-threaded programs don't call it (at least those using 
cthreads) and if the program isn't multi-threaded the call to 
INITTLS is most likely not needed so I suspect this would fix most 
use cases. My main non-gui program (multi-threaded) runs fine. 
However on Fedora 29 32 bit builds on 64 bit systems are broken 
for lazarus because the 32 bit -devel packages are broken:


https://bugzilla.redhat.com/show_bug.cgi?id=1651231

https://bugzilla.redhat.com/show_bug.cgi?id=1645328

so maybe I should just conclude that 32 bit apps are broken on 
Fedora.


Colin

___
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal


Can you test if patch from my bug report 
https://bugs.freepascal.org/view.php?id=34475> fixes your 
problem? You can omit changes for x86_64 target from that patch.



___
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal


This is loader-abitag.diff? With that applied, both 64 and 32 bit 
fpc trunk build, and basic testing indicates that they are working 
fine. I note however that compiling a basic "Hello World" program 
now produces a dynamically linked, rather than a statically linked 
executable, and INITTLS is not called.


Colin

___
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal


Strange. All my (32/64 bits) binaries are static ones.

What I can see at seeing the source code is that INITTLS is only 
defined for i386 target.


___
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal


Oh, I forgot to mention that I use Arch Linux. I run the i686 and 
x86_64 versions of Arch as an LXC containers.


___
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal


Sorry - my statement about "Hello World" producing a dynamically linked 
executable was wrong - I must have mixed up the source file. It now 
behaves as I would expect, and can recommend your patch. I will add a 
note in the bug tracker


Colin

___
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal

Re: [fpc-pascal] Building trunk

2018-11-30 Thread Cyrax 

On 30/11/2018 12:23, Cyrax wrote:

On 30/11/2018 11:12, C Western wrote:

On 30/11/2018 04:23, Cyrax wrote:

On 30/11/2018 00:53, C Western wrote:

On 26/11/2018 22:46, - - wrote:
An additional note - it may well be a ld version issue. On Ubuntu 
the ld version is 2.30, but on Fedora ld reports 2.31.1-13.fc29. 
(Maybe I should have held off upgrading to Fedora 29...)


Colin
___
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal


Looking at this a little more I think the headers are simply not 
available to the program. Simply commenting out the INITTLS call 
allows the compiler to be built successfully. I note that 
multi-threaded programs don't call it (at least those using 
cthreads) and if the program isn't multi-threaded the call to 
INITTLS is most likely not needed so I suspect this would fix most 
use cases. My main non-gui program (multi-threaded) runs fine. 
However on Fedora 29 32 bit builds on 64 bit systems are broken for 
lazarus because the 32 bit -devel packages are broken:


https://bugzilla.redhat.com/show_bug.cgi?id=1651231

https://bugzilla.redhat.com/show_bug.cgi?id=1645328

so maybe I should just conclude that 32 bit apps are broken on Fedora.

Colin

___
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal


Can you test if patch from my bug report 
https://bugs.freepascal.org/view.php?id=34475> fixes your 
problem? You can omit changes for x86_64 target from that patch.



___
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal


This is loader-abitag.diff? With that applied, both 64 and 32 bit fpc 
trunk build, and basic testing indicates that they are working fine. I 
note however that compiling a basic "Hello World" program now produces 
a dynamically linked, rather than a statically linked executable, and 
INITTLS is not called.


Colin

___
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal


Strange. All my (32/64 bits) binaries are static ones.

What I can see at seeing the source code is that INITTLS is only defined 
for i386 target.


___
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal


Oh, I forgot to mention that I use Arch Linux. I run the i686 and x86_64 
versions of Arch as an LXC containers.


___
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal

Re: [fpc-pascal] Building trunk

2018-11-30 Thread Cyrax 

On 30/11/2018 11:12, C Western wrote:

On 30/11/2018 04:23, Cyrax wrote:

On 30/11/2018 00:53, C Western wrote:

On 26/11/2018 22:46, - - wrote:
An additional note - it may well be a ld version issue. On Ubuntu 
the ld version is 2.30, but on Fedora ld reports 2.31.1-13.fc29. 
(Maybe I should have held off upgrading to Fedora 29...)


Colin
___
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal


Looking at this a little more I think the headers are simply not 
available to the program. Simply commenting out the INITTLS call 
allows the compiler to be built successfully. I note that 
multi-threaded programs don't call it (at least those using cthreads) 
and if the program isn't multi-threaded the call to INITTLS is most 
likely not needed so I suspect this would fix most use cases. My main 
non-gui program (multi-threaded) runs fine. However on Fedora 29 32 
bit builds on 64 bit systems are broken for lazarus because the 32 
bit -devel packages are broken:


https://bugzilla.redhat.com/show_bug.cgi?id=1651231

https://bugzilla.redhat.com/show_bug.cgi?id=1645328

so maybe I should just conclude that 32 bit apps are broken on Fedora.

Colin

___
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal


Can you test if patch from my bug report 
https://bugs.freepascal.org/view.php?id=34475> fixes your 
problem? You can omit changes for x86_64 target from that patch.



___
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal


This is loader-abitag.diff? With that applied, both 64 and 32 bit fpc 
trunk build, and basic testing indicates that they are working fine. I 
note however that compiling a basic "Hello World" program now produces a 
dynamically linked, rather than a statically linked executable, and 
INITTLS is not called.


Colin

___
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal


Strange. All my (32/64 bits) binaries are static ones.

What I can see at seeing the source code is that INITTLS is only defined 
for i386 target.


___
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal

Re: [fpc-pascal] Building trunk

2018-11-30 Thread C Western 

On 30/11/2018 04:23, Cyrax wrote:

On 30/11/2018 00:53, C Western wrote:

On 26/11/2018 22:46, - - wrote:
An additional note - it may well be a ld version issue. On Ubuntu 
the ld version is 2.30, but on Fedora ld reports 2.31.1-13.fc29. 
(Maybe I should have held off upgrading to Fedora 29...)


Colin
___
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal


Looking at this a little more I think the headers are simply not 
available to the program. Simply commenting out the INITTLS call 
allows the compiler to be built successfully. I note that 
multi-threaded programs don't call it (at least those using cthreads) 
and if the program isn't multi-threaded the call to INITTLS is most 
likely not needed so I suspect this would fix most use cases. My main 
non-gui program (multi-threaded) runs fine. However on Fedora 29 32 
bit builds on 64 bit systems are broken for lazarus because the 32 
bit -devel packages are broken:


https://bugzilla.redhat.com/show_bug.cgi?id=1651231

https://bugzilla.redhat.com/show_bug.cgi?id=1645328

so maybe I should just conclude that 32 bit apps are broken on Fedora.

Colin

___
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal


Can you test if patch from my bug report 
https://bugs.freepascal.org/view.php?id=34475> fixes your 
problem? You can omit changes for x86_64 target from that patch.



___
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal


This is loader-abitag.diff? With that applied, both 64 and 32 bit fpc 
trunk build, and basic testing indicates that they are working fine. I 
note however that compiling a basic "Hello World" program now produces a 
dynamically linked, rather than a statically linked executable, and 
INITTLS is not called.


Colin

___
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal

Re: [fpc-pascal] Building trunk

2018-11-29 Thread Cyrax 

On 30/11/2018 00:53, C Western wrote:

On 26/11/2018 22:46, - - wrote:
An additional note - it may well be a ld version issue. On Ubuntu the 
ld version is 2.30, but on Fedora ld reports 2.31.1-13.fc29. (Maybe I 
should have held off upgrading to Fedora 29...)


Colin
___
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal


Looking at this a little more I think the headers are simply not 
available to the program. Simply commenting out the INITTLS call allows 
the compiler to be built successfully. I note that multi-threaded 
programs don't call it (at least those using cthreads) and if the 
program isn't multi-threaded the call to INITTLS is most likely not 
needed so I suspect this would fix most use cases. My main non-gui 
program (multi-threaded) runs fine. However on Fedora 29 32 bit builds 
on 64 bit systems are broken for lazarus because the 32 bit -devel 
packages are broken:


https://bugzilla.redhat.com/show_bug.cgi?id=1651231

https://bugzilla.redhat.com/show_bug.cgi?id=1645328

so maybe I should just conclude that 32 bit apps are broken on Fedora.

Colin

___
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal


Can you test if patch from my bug report 
https://bugs.freepascal.org/view.php?id=34475> fixes your problem? 
You can omit changes for x86_64 target from that patch.



___
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal

Re: [fpc-pascal] Building trunk

2018-11-29 Thread C Western 

On 26/11/2018 22:46, - - wrote:

An additional note - it may well be a ld version issue. On Ubuntu the ld 
version is 2.30, but on Fedora ld reports 2.31.1-13.fc29. (Maybe I should have 
held off upgrading to Fedora 29...)

Colin
___
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal


Looking at this a little more I think the headers are simply not 
available to the program. Simply commenting out the INITTLS call allows 
the compiler to be built successfully. I note that multi-threaded 
programs don't call it (at least those using cthreads) and if the 
program isn't multi-threaded the call to INITTLS is most likely not 
needed so I suspect this would fix most use cases. My main non-gui 
program (multi-threaded) runs fine. However on Fedora 29 32 bit builds 
on 64 bit systems are broken for lazarus because the 32 bit -devel 
packages are broken:


https://bugzilla.redhat.com/show_bug.cgi?id=1651231

https://bugzilla.redhat.com/show_bug.cgi?id=1645328

so maybe I should just conclude that 32 bit apps are broken on Fedora.

Colin

___
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal

Re: [fpc-pascal] Building trunk

2018-11-26 Thread - - 
An additional note - it may well be a ld version issue. On Ubuntu the ld 
version is 2.30, but on Fedora ld reports 2.31.1-13.fc29. (Maybe I should have 
held off upgrading to Fedora 29...)

Colin
___
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal

Re: [fpc-pascal] Building trunk

2018-11-25 Thread Cyrax 

On 25/11/2018 14:58, Jonas Maebe wrote:

On 25/11/18 13:51, Florian Klämpfl wrote:
I am not aware that somewhere a fixed offset is applied. All info is 
read from the auxiliary data and the header.


You can have a load address offset in case there is a PT_PHDR. From 
http://www.gabriel.urdhr.fr/2015/01/22/elf-linking/ :


// Simplified code from the GNU dynamic linker source code:
for (ph = phdr; ph < [phnum]; ++ph)
   if (ph->p_type == PT_PHDR)
     main_map->l_addr = (ElfW(Addr)) phdr - ph->p_vaddr;

There doesn't seem to be one in Colin's program though.


Jonas
___
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal


Somehow this thread reminds my one open bug : 
https://bugs.freepascal.org/view.php?id=34475


I have found out that you need to have either linked against libc or 
have small binary stub generated from assembler source (like 64-bit 
pascal programs/libraries have that doesn't link against libc) linked 
against your 32-bit program so it can access PHDR structure without 
crashing on access violation exception.


___
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal

Re: [fpc-pascal] Building trunk

2018-11-25 Thread C Western 

On 25/11/2018 14:18, Florian Klämpfl wrote:

Am 25.11.2018 um 14:30 schrieb Colin Western:

What generates the header? Is it fpc, an external linker or the loader?


Can you please run the following C program:

#include 
#include 

int main()
{
   printf("AT_PHDR: %lx\n",getauxval(AT_PHDR));
   printf("AT_PHNUM: %lx\n",getauxval(AT_PHNUM));
}

and include also the relevant part of an objdump?
___
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal


gcc -m32 -g florian.c

./a.out
AT_PHDR: 8048034
AT_PHNUM: b

objdump -x a.out | more

a.out: file format elf32-i386
a.out
architecture: i386, flags 0x0112:
EXEC_P, HAS_SYMS, D_PAGED
start address 0x08049070

Program Header:
    PHDR off    0x0034 vaddr 0x08048034 paddr 0x08048034 align 2**2
 filesz 0x0160 memsz 0x0160 flags r--
  INTERP off    0x0194 vaddr 0x08048194 paddr 0x08048194 align 2**0
 filesz 0x0013 memsz 0x0013 flags r--
    LOAD off    0x vaddr 0x08048000 paddr 0x08048000 align 2**12
 filesz 0x032c memsz 0x032c flags r--
    LOAD off    0x1000 vaddr 0x08049000 paddr 0x08049000 align 2**12
 filesz 0x0260 memsz 0x0260 flags r-x
    LOAD off    0x2000 vaddr 0x0804a000 paddr 0x0804a000 align 2**12
 filesz 0x015c memsz 0x015c flags r--
    LOAD off    0x2f0c vaddr 0x0804bf0c paddr 0x0804bf0c align 2**12
 filesz 0x0110 memsz 0x0114 flags rw-
 DYNAMIC off    0x2f14 vaddr 0x0804bf14 paddr 0x0804bf14 align 2**2
 filesz 0x00e8 memsz 0x00e8 flags rw-
    NOTE off    0x01a8 vaddr 0x080481a8 paddr 0x080481a8 align 2**2
 filesz 0x0044 memsz 0x0044 flags r--
EH_FRAME off    0x202c vaddr 0x0804a02c paddr 0x0804a02c align 2**2
 filesz 0x003c memsz 0x003c flags r--
   STACK off    0x vaddr 0x paddr 0x align 2**4
 filesz 0x memsz 0x flags rw-
   RELRO off    0x2f0c vaddr 0x0804bf0c paddr 0x0804bf0c align 2**0
 filesz 0x00f4 memsz 0x00f4 flags r--

Dynamic Section:
  NEEDED   libc.so.6
  INIT 0x08049000
  FINI 0x08049248
  INIT_ARRAY   0x0804bf0c
  INIT_ARRAYSZ 0x0004
  FINI_ARRAY   0x0804bf10
  FINI_ARRAYSZ 0x0004
  GNU_HASH 0x080481ec
  STRTAB   0x0804826c
  SYMTAB   0x0804820c
  STRSZ    0x0061
  SYMENT   0x0010
  DEBUG    0x
  PLTGOT   0x0804c000
  PLTRELSZ 0x0018
  PLTREL   0x0011
  JMPREL   0x08048314
  REL  0x0804830c
  RELSZ    0x0008
  RELENT   0x0008
  VERNEED  0x080482dc
  VERNEEDNUM   0x0001
  VERSYM   0x080482ce

Version References:
  required from libc.so.6:
    0x06969196 0x00 03 GLIBC_2.16
    0x0d696910 0x00 02 GLIBC_2.0

Sections:
Idx Name  Size  VMA   LMA   File off  Algn
  0 .interp   0013  08048194  08048194  0194  2**0
  CONTENTS, ALLOC, LOAD, READONLY, DATA
  1 .note.ABI-tag 0020  080481a8  080481a8  01a8  2**2
  CONTENTS, ALLOC, LOAD, READONLY, DATA
  2 .note.gnu.build-id 0024  080481c8  080481c8  01c8 2**2
  CONTENTS, ALLOC, LOAD, READONLY, DATA
  3 .gnu.hash 0020  080481ec  080481ec  01ec  2**2
  CONTENTS, ALLOC, LOAD, READONLY, DATA
  4 .dynsym   0060  0804820c  0804820c  020c  2**2
  CONTENTS, ALLOC, LOAD, READONLY, DATA
  5 .dynstr   0061  0804826c  0804826c  026c  2**0
  CONTENTS, ALLOC, LOAD, READONLY, DATA
  6 .gnu.version  000c  080482ce  080482ce  02ce  2**1
  CONTENTS, ALLOC, LOAD, READONLY, DATA
  7 .gnu.version_r 0030  080482dc  080482dc  02dc  2**2
  CONTENTS, ALLOC, LOAD, READONLY, DATA
  8 .rel.dyn  0008  0804830c  0804830c  030c  2**2
  CONTENTS, ALLOC, LOAD, READONLY, DATA
  9 .rel.plt  0018  08048314  08048314  0314  2**2
  CONTENTS, ALLOC, LOAD, READONLY, DATA
 10 .init 0024  08049000  08049000  1000  2**2
  CONTENTS, ALLOC, LOAD, READONLY, CODE
 11 .plt  0040  08049030  08049030  1030  2**4
  CONTENTS, ALLOC, LOAD, READONLY, CODE
 12 .text 01d5  08049070  08049070  1070  2**4
  CONTENTS, ALLOC, LOAD, READONLY, CODE
 13 .fini 0018  08049248  08049248  1248  2**2
  CONTENTS, ALLOC, LOAD, READONLY, CODE
 14 .rodata   0029  0804a000  0804a000  2000  2**2
  CONTENTS, ALLOC, LOAD, READONLY, DATA
 15 .eh_frame_hdr 003c 

Re: [fpc-pascal] Building trunk

2018-11-25 Thread Florian Klämpfl 
Am 25.11.2018 um 14:30 schrieb Colin Western:
> What generates the header? Is it fpc, an external linker or the loader?
> 

Can you please run the following C program:

#include 
#include 

int main()
{
  printf("AT_PHDR: %lx\n",getauxval(AT_PHDR));
  printf("AT_PHNUM: %lx\n",getauxval(AT_PHNUM));
}

and include also the relevant part of an objdump?
___
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal

Re: [fpc-pascal] Building trunk

2018-11-25 Thread Jonas Maebe 

On 25/11/18 14:30, Colin Western wrote:

What generates the header? Is it fpc, an external linker or the loader?


The linker.


Jonas
___
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal

Re: [fpc-pascal] Building trunk

2018-11-25 Thread Colin Western 
What generates the header? Is it fpc, an external linker or the loader?

Colin
Sent from my mobile.
___
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal

Re: [fpc-pascal] Building trunk

2018-11-25 Thread Florian Klämpfl 
Am 25.11.2018 um 13:58 schrieb Jonas Maebe:
> On 25/11/18 13:51, Florian Klämpfl wrote:
>> I am not aware that somewhere a fixed offset is applied. All info is read 
>> from the auxiliary data and the header.
> 
> You can have a load address offset in case there is a PT_PHDR. 

Yes.

> From http://www.gabriel.urdhr.fr/2015/01/22/elf-linking/ :
> 
> // Simplified code from the GNU dynamic linker source code:
> for (ph = phdr; ph < [phnum]; ++ph)
>   if (ph->p_type == PT_PHDR)
>     main_map->l_addr = (ElfW(Addr)) phdr - ph->p_vaddr;
> 
> There doesn't seem to be one in Colin's program though.

Indeed. The program header itself seems to be wrong/interpreted wrong.
___
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal

Re: [fpc-pascal] Building trunk

2018-11-25 Thread Jonas Maebe 

On 25/11/18 13:51, Florian Klämpfl wrote:

I am not aware that somewhere a fixed offset is applied. All info is read from 
the auxiliary data and the header.


You can have a load address offset in case there is a PT_PHDR. From 
http://www.gabriel.urdhr.fr/2015/01/22/elf-linking/ :


// Simplified code from the GNU dynamic linker source code:
for (ph = phdr; ph < [phnum]; ++ph)
  if (ph->p_type == PT_PHDR)
main_map->l_addr = (ElfW(Addr)) phdr - ph->p_vaddr;

There doesn't seem to be one in Colin's program though.


Jonas
___
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal

Re: [fpc-pascal] Building trunk

2018-11-25 Thread Florian Klämpfl 
Am 25.11.2018 um 13:51 schrieb Florian Klämpfl:
> Am 25.11.2018 um 13:06 schrieb C Western:
> fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
> http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
 That gives the same value as shown above, even after applying the patch. 
 Single stepping the code indicates that both
 variables are assigned: (Some lines deleted).
>>> This is pretty strange then. This code is pretty simple and in general, tls 
>>> initialization should be done regardless if
>>> FPC uses it for threadvars or not. What version of Fedora are you using?
>>> ___
>>> fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
>>> http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
>>
>> Fedora 29 (64 bit). Did you see my other message in the thread about a 
>> different offset in program header when compiled
>> under Fedora and Ubuntu? (It works on Ubuntu). It is though an offset needs 
>> to be applied to find the program header,
>> but I can't see where to find it.
> 
> I am not aware that somewhere a fixed offset is applied. All info is read 
> from the auxiliary data and the header.
> 

You mean the offset field in the header? I cannot imaging how the offset in the 
header could influence the header itself?
___
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal

Re: [fpc-pascal] Building trunk

2018-11-25 Thread Florian Klämpfl 
Am 25.11.2018 um 13:06 schrieb C Western:
 fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
 http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
>>> That gives the same value as shown above, even after applying the patch. 
>>> Single stepping the code indicates that both
>>> variables are assigned: (Some lines deleted).
>> This is pretty strange then. This code is pretty simple and in general, tls 
>> initialization should be done regardless if
>> FPC uses it for threadvars or not. What version of Fedora are you using?
>> ___
>> fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
>> http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
> 
> Fedora 29 (64 bit). Did you see my other message in the thread about a 
> different offset in program header when compiled
> under Fedora and Ubuntu? (It works on Ubuntu). It is though an offset needs 
> to be applied to find the program header,
> but I can't see where to find it.

I am not aware that somewhere a fixed offset is applied. All info is read from 
the auxiliary data and the header.

___
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal

Re: [fpc-pascal] Building trunk

2018-11-25 Thread C Western 

On 25/11/2018 12:01, Florian Klämpfl wrote:

Am 25.11.2018 um 12:20 schrieb C Western:

On 24/11/2018 22:21, Florian Klämpfl wrote:

Am 24.11.2018 um 10:08 schrieb C Western:

On 23/11/2018 09:50, Sven Barth via fpc-pascal wrote:

Am Fr., 23. Nov. 2018, 10:26 hat C Western mailto:l...@c-m-w.me.uk>> geschrieben:

  I haven't been able to build trunk i386 fpc for a couple of weeks. Is
  this supposed to be working, or have I misconfigured something? (I
  don't
  think I have changed anything.) The output is below. I don't think
  it is
  significant, but I am building on a 64 bit system, but with a 32 bit
  starting compiler. (The 64 bit build with the 64 bit starting
  compiler
  works fine.)


We have i386 trunk building on at least one x86_64-linux machine, so it can't 
be a principal problem. :/
Could you check whether it's FPC itself that segfaults or something else and if 
the former try to retrieve a
stacktrace, please?

Regards,
Sven

___
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal

Looks like the ppc1 compiler crashes during setup:

gdb) run
Starting program: /home/me/fpc/trunk/fpcsrc/compiler/ppc1

Program received signal SIGSEGV, Segmentation fault.
0x08068760 in INITTLS () at system.pp:543
543        case phdr^.p_type of
(gdb) bt
#0  0x08068760 in INITTLS () at system.pp:543
#1  0x082a63fb in _FPC_PROC_START () at ./i386/si_prc.inc:105
(gdb) p phdr
$1 = (PPHDR) 0x8048034
(gdb) p phdr^
Cannot access memory at address 0x8048034

Can you please check what value phdr has at the crash location after applying 
the following patch?

diff --git a/rtl/linux/system.pp b/rtl/linux/system.pp
index 0d7ed2b152..74b4592ace 100644
--- a/rtl/linux/system.pp
+++ b/rtl/linux/system.pp
@@ -525,6 +525,8 @@ procedure InitTLS; [public,alias:'FPC_INITTLS'];
   while assigned(auxp^) do
     inc(auxp);
   inc(auxp);
+    phdr:=nil;
+    phnum:=0;
   { now we are at the auxillary vector }
   while assigned(auxp^) do
     begin
___
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal

That gives the same value as shown above, even after applying the patch. Single 
stepping the code indicates that both
variables are assigned: (Some lines deleted).

This is pretty strange then. This code is pretty simple and in general, tls 
initialization should be done regardless if
FPC uses it for threadvars or not. What version of Fedora are you using?
___
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal


Fedora 29 (64 bit). Did you see my other message in the thread about a 
different offset in program header when compiled under Fedora and 
Ubuntu? (It works on Ubuntu). It is though an offset needs to be applied 
to find the program header, but I can't see where to find it.


Colin

___
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal

Re: [fpc-pascal] Building trunk

2018-11-25 Thread Florian Klämpfl 
Am 25.11.2018 um 12:20 schrieb C Western:
> On 24/11/2018 22:21, Florian Klämpfl wrote:
>> Am 24.11.2018 um 10:08 schrieb C Western:
>>> On 23/11/2018 09:50, Sven Barth via fpc-pascal wrote:
 Am Fr., 23. Nov. 2018, 10:26 hat C Western >>> > geschrieben:

  I haven't been able to build trunk i386 fpc for a couple of weeks. Is
  this supposed to be working, or have I misconfigured something? (I
  don't
  think I have changed anything.) The output is below. I don't think
  it is
  significant, but I am building on a 64 bit system, but with a 32 bit
  starting compiler. (The 64 bit build with the 64 bit starting
  compiler
  works fine.)


 We have i386 trunk building on at least one x86_64-linux machine, so it 
 can't be a principal problem. :/
 Could you check whether it's FPC itself that segfaults or something else 
 and if the former try to retrieve a
 stacktrace, please?

 Regards,
 Sven

 ___
 fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
 http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
>>> Looks like the ppc1 compiler crashes during setup:
>>>
>>> gdb) run
>>> Starting program: /home/me/fpc/trunk/fpcsrc/compiler/ppc1
>>>
>>> Program received signal SIGSEGV, Segmentation fault.
>>> 0x08068760 in INITTLS () at system.pp:543
>>> 543        case phdr^.p_type of
>>> (gdb) bt
>>> #0  0x08068760 in INITTLS () at system.pp:543
>>> #1  0x082a63fb in _FPC_PROC_START () at ./i386/si_prc.inc:105
>>> (gdb) p phdr
>>> $1 = (PPHDR) 0x8048034
>>> (gdb) p phdr^
>>> Cannot access memory at address 0x8048034
>> Can you please check what value phdr has at the crash location after 
>> applying the following patch?
>>
>> diff --git a/rtl/linux/system.pp b/rtl/linux/system.pp
>> index 0d7ed2b152..74b4592ace 100644
>> --- a/rtl/linux/system.pp
>> +++ b/rtl/linux/system.pp
>> @@ -525,6 +525,8 @@ procedure InitTLS; [public,alias:'FPC_INITTLS'];
>>   while assigned(auxp^) do
>>     inc(auxp);
>>   inc(auxp);
>> +    phdr:=nil;
>> +    phnum:=0;
>>   { now we are at the auxillary vector }
>>   while assigned(auxp^) do
>>     begin
>> ___
>> fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
>> http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
> 
> That gives the same value as shown above, even after applying the patch. 
> Single stepping the code indicates that both
> variables are assigned: (Some lines deleted).

This is pretty strange then. This code is pretty simple and in general, tls 
initialization should be done regardless if
FPC uses it for threadvars or not. What version of Fedora are you using?
___
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal

Re: [fpc-pascal] Building trunk

2018-11-25 Thread C Western 

On 24/11/2018 22:21, Florian Klämpfl wrote:

Am 24.11.2018 um 10:08 schrieb C Western:

On 23/11/2018 09:50, Sven Barth via fpc-pascal wrote:

Am Fr., 23. Nov. 2018, 10:26 hat C Western mailto:l...@c-m-w.me.uk>> geschrieben:

     I haven't been able to build trunk i386 fpc for a couple of weeks. Is
     this supposed to be working, or have I misconfigured something? (I
     don't
     think I have changed anything.) The output is below. I don't think
     it is
     significant, but I am building on a 64 bit system, but with a 32 bit
     starting compiler. (The 64 bit build with the 64 bit starting
     compiler
     works fine.)


We have i386 trunk building on at least one x86_64-linux machine, so it can't 
be a principal problem. :/
Could you check whether it's FPC itself that segfaults or something else and if 
the former try to retrieve a
stacktrace, please?

Regards,
Sven

___
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal

Looks like the ppc1 compiler crashes during setup:

gdb) run
Starting program: /home/me/fpc/trunk/fpcsrc/compiler/ppc1

Program received signal SIGSEGV, Segmentation fault.
0x08068760 in INITTLS () at system.pp:543
543        case phdr^.p_type of
(gdb) bt
#0  0x08068760 in INITTLS () at system.pp:543
#1  0x082a63fb in _FPC_PROC_START () at ./i386/si_prc.inc:105
(gdb) p phdr
$1 = (PPHDR) 0x8048034
(gdb) p phdr^
Cannot access memory at address 0x8048034

Can you please check what value phdr has at the crash location after applying 
the following patch?

diff --git a/rtl/linux/system.pp b/rtl/linux/system.pp
index 0d7ed2b152..74b4592ace 100644
--- a/rtl/linux/system.pp
+++ b/rtl/linux/system.pp
@@ -525,6 +525,8 @@ procedure InitTLS; [public,alias:'FPC_INITTLS'];
  while assigned(auxp^) do
inc(auxp);
  inc(auxp);
+phdr:=nil;
+phnum:=0;
  { now we are at the auxillary vector }
  while assigned(auxp^) do
begin
___
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal


That gives the same value as shown above, even after applying the patch. 
Single stepping the code indicates that both variables are assigned: 
(Some lines deleted).


Breakpoint 1, INITTLS () at system.pp:523
523        auxp:=ppointer(envp);
(gdb) n
525        while assigned(auxp^) do
(gdb) n
533        case plongint(auxp)^ of
(gdb) n
535        phdr:=pphdr(ppointer(auxp+1)^);
(gdb) n
539        inc(auxp,2);
(gdb) p phdr
$3 = (PPHDR) 0x8048034
(gdb) p phdr^
Cannot access memory at address 0x8048034
(gdb) n
533        case plongint(auxp)^ of
(gdb) n
539        inc(auxp,2);
(gdb) n
533        case plongint(auxp)^ of
(gdb) n
537        phnum:=pdword(auxp+1)^;
(gdb) n
539        inc(auxp,2);
(gdb) p phnum
$4 = 4
(gdb)
543        for i:=1 to phnum do
(gdb) n
545        case phdr^.p_type of
(gdb) n

Program received signal SIGSEGV, Segmentation fault.
0x0806ef01 in INITTLS () at system.pp:545
545        case phdr^.p_type of
(gdb) p phdr
$5 = (PPHDR) 0x8048034
(gdb)

Colin

___
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal

Re: [fpc-pascal] Building trunk

2018-11-24 Thread Florian Klämpfl 
Am 24.11.2018 um 10:08 schrieb C Western:
> On 23/11/2018 09:50, Sven Barth via fpc-pascal wrote:
>> Am Fr., 23. Nov. 2018, 10:26 hat C Western > > geschrieben:
>>
>>     I haven't been able to build trunk i386 fpc for a couple of weeks. Is
>>     this supposed to be working, or have I misconfigured something? (I
>>     don't
>>     think I have changed anything.) The output is below. I don't think
>>     it is
>>     significant, but I am building on a 64 bit system, but with a 32 bit
>>     starting compiler. (The 64 bit build with the 64 bit starting
>>     compiler
>>     works fine.)
>>
>>
>> We have i386 trunk building on at least one x86_64-linux machine, so it 
>> can't be a principal problem. :/
>> Could you check whether it's FPC itself that segfaults or something else and 
>> if the former try to retrieve a
>> stacktrace, please?
>>
>> Regards,
>> Sven
>>
>> ___
>> fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
>> http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
> 
> Looks like the ppc1 compiler crashes during setup:
> 
> gdb) run
> Starting program: /home/me/fpc/trunk/fpcsrc/compiler/ppc1
> 
> Program received signal SIGSEGV, Segmentation fault.
> 0x08068760 in INITTLS () at system.pp:543
> 543        case phdr^.p_type of
> (gdb) bt
> #0  0x08068760 in INITTLS () at system.pp:543
> #1  0x082a63fb in _FPC_PROC_START () at ./i386/si_prc.inc:105
> (gdb) p phdr
> $1 = (PPHDR) 0x8048034
> (gdb) p phdr^
> Cannot access memory at address 0x8048034

Can you please check what value phdr has at the crash location after applying 
the following patch?

diff --git a/rtl/linux/system.pp b/rtl/linux/system.pp
index 0d7ed2b152..74b4592ace 100644
--- a/rtl/linux/system.pp
+++ b/rtl/linux/system.pp
@@ -525,6 +525,8 @@ procedure InitTLS; [public,alias:'FPC_INITTLS'];
 while assigned(auxp^) do
   inc(auxp);
 inc(auxp);
+phdr:=nil;
+phnum:=0;
 { now we are at the auxillary vector }
 while assigned(auxp^) do
   begin
___
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal

Re: [fpc-pascal] Building trunk

2018-11-24 Thread C Western 

On 24/11/2018 15:19, C Western wrote:

On 24/11/2018 12:30, Sven Barth via fpc-pascal wrote:
Am Sa., 24. Nov. 2018, 10:09 hat C Western > geschrieben:


    On 23/11/2018 09:50, Sven Barth via fpc-pascal wrote:
    > Am Fr., 23. Nov. 2018, 10:26 hat C Western mailto:l...@c-m-w.me.uk>
    > >> geschrieben:
    >
    >     I haven't been able to build trunk i386 fpc for a couple of
    weeks. Is
    >     this supposed to be working, or have I misconfigured
    something? (I
    >     don't
    >     think I have changed anything.) The output is below. I don't
    think
    >     it is
    >     significant, but I am building on a 64 bit system, but with
    a 32 bit
    >     starting compiler. (The 64 bit build with the 64 bit starting
    >     compiler
    >     works fine.)
    >
    >
    > We have i386 trunk building on at least one x86_64-linux
    machine, so
    > it can't be a principal problem. :/
    > Could you check whether it's FPC itself that segfaults or 
something

    > else and if the former try to retrieve a stacktrace, please?
    >
    > Regards,
    > Sven
    >
    > ___
    > fpc-pascal maillist  - fpc-pascal@lists.freepascal.org
    
    > http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal

    Looks like the ppc1 compiler crashes during setup:

    gdb) run
    Starting program: /home/me/fpc/trunk/fpcsrc/compiler/ppc1

    Program received signal SIGSEGV, Segmentation fault.
    0x08068760 in INITTLS () at system.pp:543
    543        case phdr^.p_type of
    (gdb) bt
    #0  0x08068760 in INITTLS () at system.pp:543
    #1  0x082a63fb in _FPC_PROC_START () at ./i386/si_prc.inc:105
    (gdb) p phdr
    $1 = (PPHDR) 0x8048034
    (gdb) p phdr^
    Cannot access memory at address 0x8048034


Looks like something related to the new threadvar handling. Though by 
default that shouldn't be enabled... 樂


Regards,
Sven

___
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal


Some more information:

It seems to work fine on Ubuntu (32 bit built on 64 bit OS, same 
machine). Comparing the binaries with objdump, it looks as though the 
Fedora one has an offset of 1000, which the Ununtu one does not, and 
the offset of 1000 needs to be applied to the program header address, 
but is not. On Fedora:


ppc1: file format elf32-i386
ppc1
architecture: i386, flags 0x0112:
EXEC_P, HAS_SYMS, D_PAGED
start address 0x082a63d0

Program Header:
    LOAD off    0x1000 vaddr 0x08049000 paddr 0x08049000 align 2**12
 filesz 0x0025d450 memsz 0x0025d450 flags r-x
    LOAD off    0x0025f000 vaddr 0x082a7000 paddr 0x082a7000 align 2**12
 filesz 0x00020f04 memsz 0x00020f04 flags r--
    LOAD off    0x0028 vaddr 0x082c8000 paddr 0x082c8000 align 2**12
 filesz 0x000f7280 memsz 0x00102d84 flags rw-
   STACK off    0x vaddr 0x paddr 0x align 2**4
 filesz 0x memsz 0x flags rw-

On Ubuntu:

./ppc1: file format elf32-i386
./ppc1
architecture: i386, flags 0x0112:
EXEC_P, HAS_SYMS, D_PAGED
start address 0x082a5470

Program Header:
    LOAD off    0x vaddr 0x08048000 paddr 0x08048000 align 2**12
 filesz 0x0027e3f4 memsz 0x0027e3f4 flags r-x
    LOAD off    0x0027f000 vaddr 0x082c7000 paddr 0x082c7000 align 2**12
 filesz 0x000f7280 memsz 0x00102d84 flags rw-
   STACK off    0x vaddr 0x paddr 0x align 2**4
 filesz 0x memsz 0x flags rw-

gdb indicates both versions try to access 0x8048034, but this is not 
mapped on the Fedora version.


Colin

___
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal


And going through the versions indicates the problem is introduced by:

r40272 | florian | 2018-11-07 22:03:02 + (Wed, 07 Nov 2018) | 1 line
Changed paths:
   M /trunk/compiler/cgbase.pas
   M /trunk/compiler/x86/agx86att.pas
   M /trunk/compiler/x86/cgx86.pas
   M /trunk/compiler/x86/nx86ld.pas
   M /trunk/rtl/linux/i386/si_prc.inc
   M /trunk/rtl/linux/system.pp

+ i386-linux support for tls-based threadvars

___
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal

Re: [fpc-pascal] Building trunk

2018-11-24 Thread C Western 

On 24/11/2018 12:30, Sven Barth via fpc-pascal wrote:
Am Sa., 24. Nov. 2018, 10:09 hat C Western > geschrieben:


On 23/11/2018 09:50, Sven Barth via fpc-pascal wrote:
> Am Fr., 23. Nov. 2018, 10:26 hat C Western mailto:l...@c-m-w.me.uk>
> >> geschrieben:
>
>     I haven't been able to build trunk i386 fpc for a couple of
weeks. Is
>     this supposed to be working, or have I misconfigured
something? (I
>     don't
>     think I have changed anything.) The output is below. I don't
think
>     it is
>     significant, but I am building on a 64 bit system, but with
a 32 bit
>     starting compiler. (The 64 bit build with the 64 bit starting
>     compiler
>     works fine.)
>
>
> We have i386 trunk building on at least one x86_64-linux
machine, so
> it can't be a principal problem. :/
> Could you check whether it's FPC itself that segfaults or something
> else and if the former try to retrieve a stacktrace, please?
>
> Regards,
> Sven
>
> ___
> fpc-pascal maillist  - fpc-pascal@lists.freepascal.org

> http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal

Looks like the ppc1 compiler crashes during setup:

gdb) run
Starting program: /home/me/fpc/trunk/fpcsrc/compiler/ppc1

Program received signal SIGSEGV, Segmentation fault.
0x08068760 in INITTLS () at system.pp:543
543        case phdr^.p_type of
(gdb) bt
#0  0x08068760 in INITTLS () at system.pp:543
#1  0x082a63fb in _FPC_PROC_START () at ./i386/si_prc.inc:105
(gdb) p phdr
$1 = (PPHDR) 0x8048034
(gdb) p phdr^
Cannot access memory at address 0x8048034


Looks like something related to the new threadvar handling. Though by 
default that shouldn't be enabled... 樂


Regards,
Sven

___
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal


Some more information:

It seems to work fine on Ubuntu (32 bit built on 64 bit OS, same 
machine). Comparing the binaries with objdump, it looks as though the 
Fedora one has an offset of 1000, which the Ununtu one does not, and the 
offset of 1000 needs to be applied to the program header address, but is 
not. On Fedora:


ppc1: file format elf32-i386
ppc1
architecture: i386, flags 0x0112:
EXEC_P, HAS_SYMS, D_PAGED
start address 0x082a63d0

Program Header:
    LOAD off    0x1000 vaddr 0x08049000 paddr 0x08049000 align 2**12
 filesz 0x0025d450 memsz 0x0025d450 flags r-x
    LOAD off    0x0025f000 vaddr 0x082a7000 paddr 0x082a7000 align 2**12
 filesz 0x00020f04 memsz 0x00020f04 flags r--
    LOAD off    0x0028 vaddr 0x082c8000 paddr 0x082c8000 align 2**12
 filesz 0x000f7280 memsz 0x00102d84 flags rw-
   STACK off    0x vaddr 0x paddr 0x align 2**4
 filesz 0x memsz 0x flags rw-

On Ubuntu:

./ppc1: file format elf32-i386
./ppc1
architecture: i386, flags 0x0112:
EXEC_P, HAS_SYMS, D_PAGED
start address 0x082a5470

Program Header:
    LOAD off    0x vaddr 0x08048000 paddr 0x08048000 align 2**12
 filesz 0x0027e3f4 memsz 0x0027e3f4 flags r-x
    LOAD off    0x0027f000 vaddr 0x082c7000 paddr 0x082c7000 align 2**12
 filesz 0x000f7280 memsz 0x00102d84 flags rw-
   STACK off    0x vaddr 0x paddr 0x align 2**4
 filesz 0x memsz 0x flags rw-

gdb indicates both versions try to access 0x8048034, but this is not 
mapped on the Fedora version.


Colin

___
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal

Re: [fpc-pascal] Building trunk

2018-11-24 Thread Sven Barth via fpc-pascal 
Am Sa., 24. Nov. 2018, 10:09 hat C Western  geschrieben:

> On 23/11/2018 09:50, Sven Barth via fpc-pascal wrote:
> > Am Fr., 23. Nov. 2018, 10:26 hat C Western  > > geschrieben:
> >
> > I haven't been able to build trunk i386 fpc for a couple of weeks. Is
> > this supposed to be working, or have I misconfigured something? (I
> > don't
> > think I have changed anything.) The output is below. I don't think
> > it is
> > significant, but I am building on a 64 bit system, but with a 32 bit
> > starting compiler. (The 64 bit build with the 64 bit starting
> > compiler
> > works fine.)
> >
> >
> > We have i386 trunk building on at least one x86_64-linux machine, so
> > it can't be a principal problem. :/
> > Could you check whether it's FPC itself that segfaults or something
> > else and if the former try to retrieve a stacktrace, please?
> >
> > Regards,
> > Sven
> >
> > ___
> > fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
> > http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
>
> Looks like the ppc1 compiler crashes during setup:
>
> gdb) run
> Starting program: /home/me/fpc/trunk/fpcsrc/compiler/ppc1
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x08068760 in INITTLS () at system.pp:543
> 543case phdr^.p_type of
> (gdb) bt
> #0  0x08068760 in INITTLS () at system.pp:543
> #1  0x082a63fb in _FPC_PROC_START () at ./i386/si_prc.inc:105
> (gdb) p phdr
> $1 = (PPHDR) 0x8048034
> (gdb) p phdr^
> Cannot access memory at address 0x8048034
>

Looks like something related to the new threadvar handling. Though by
default that shouldn't be enabled... 樂

Regards,
Sven

>
___
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal

Re: [fpc-pascal] Building trunk

2018-11-24 Thread C Western 

On 23/11/2018 13:58, Joost van der Sluis wrote:

On 11/23/18 2:48 PM, C Western wrote:
make distclean cycle OPT="-n" OS_TARGET=linux CPU_TARGET=i386 
FPC=~/fpc/bootstrap/ppcx64


/home/ctcmw/fpc/trunk/fpcsrc/compiler/ppcross386 -Pi386 
-XPi386-linux- -Xr -Fui386 -Fusystems -Fu../rtl/units/i386-linux 
-Fii386 -FEi386/bin/i386-linux -FUi386/units/i386-linux -n -di386 
-dGDB -dBROWSERLOG -Fux86 -Sew    -di386 -dGDB -dBROWSERLOG -Fux86 
-Sew pp.pas
pp.pas(277,1) Error: Util i386-linux-ld not found, switching to 
external linking



I will try and generate a backtrace as suggested by Sven later.


No need to. The compiler does not crash. It cannot find i386-linux-ld.

You need the binutils for cross-compilation. See the buildfaq.

Or, create them yourself. Add the following bash-scripts somewhere in 
your path and make them executable: (Works on Fedora, might be 
different on other systems)


i386-linux-as:
--
#!/bin/bash
# name this file /usr/bin/i386-linux-as
as --32 $@
--

i386-linux-ld:

--
#!/bin/bash
# name this file /usr/bin/i386-linux-ld
ld -A elf32-i386 $@
--


Regards,

Joost.
___
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal


Creating i386-linux-ld allows the make distclean cycle to complete. 
However the resulting compiler (ppc386) gives a segmentation fault on 
startup, just as I had with the previous approach. See my other message 
for the stack trace.


Colin

___
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal

Re: [fpc-pascal] Building trunk

2018-11-24 Thread C Western 

On 23/11/2018 09:50, Sven Barth via fpc-pascal wrote:
Am Fr., 23. Nov. 2018, 10:26 hat C Western > geschrieben:


I haven't been able to build trunk i386 fpc for a couple of weeks. Is
this supposed to be working, or have I misconfigured something? (I
don't
think I have changed anything.) The output is below. I don't think
it is
significant, but I am building on a 64 bit system, but with a 32 bit
starting compiler. (The 64 bit build with the 64 bit starting
compiler
works fine.)


We have i386 trunk building on at least one x86_64-linux machine, so 
it can't be a principal problem. :/
Could you check whether it's FPC itself that segfaults or something 
else and if the former try to retrieve a stacktrace, please?


Regards,
Sven

___
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal


Looks like the ppc1 compiler crashes during setup:

gdb) run
Starting program: /home/me/fpc/trunk/fpcsrc/compiler/ppc1

Program received signal SIGSEGV, Segmentation fault.
0x08068760 in INITTLS () at system.pp:543
543        case phdr^.p_type of
(gdb) bt
#0  0x08068760 in INITTLS () at system.pp:543
#1  0x082a63fb in _FPC_PROC_START () at ./i386/si_prc.inc:105
(gdb) p phdr
$1 = (PPHDR) 0x8048034
(gdb) p phdr^
Cannot access memory at address 0x8048034

___
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal

Re: [fpc-pascal] Building trunk

2018-11-23 Thread Joost van der Sluis 

On 11/23/18 2:48 PM, C Western wrote:
make distclean cycle OPT="-n" OS_TARGET=linux CPU_TARGET=i386 
FPC=~/fpc/bootstrap/ppcx64


/home/ctcmw/fpc/trunk/fpcsrc/compiler/ppcross386 -Pi386 -XPi386-linux- 
-Xr -Fui386 -Fusystems -Fu../rtl/units/i386-linux -Fii386 
-FEi386/bin/i386-linux -FUi386/units/i386-linux -n -di386 -dGDB 
-dBROWSERLOG -Fux86 -Sew    -di386 -dGDB -dBROWSERLOG -Fux86 -Sew pp.pas
pp.pas(277,1) Error: Util i386-linux-ld not found, switching to external 
linking



I will try and generate a backtrace as suggested by Sven later.


No need to. The compiler does not crash. It cannot find i386-linux-ld.

You need the binutils for cross-compilation. See the buildfaq.

Or, create them yourself. Add the following bash-scripts somewhere in 
your path and make them executable: (Works on Fedora, might be different 
on other systems)


i386-linux-as:
--
#!/bin/bash
# name this file /usr/bin/i386-linux-as
as --32 $@
--

i386-linux-ld:

--
#!/bin/bash
# name this file /usr/bin/i386-linux-ld
ld -A elf32-i386 $@
--


Regards,

Joost.
___
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal

Re: [fpc-pascal] Building trunk

2018-11-23 Thread C Western 
The compiler I was starting with was obtained from a 3.0.4 release from 
the fpc website. Trying:


make distclean cycle OPT="-n" OS_TARGET=linux CPU_TARGET=i386 
FPC=~/fpc/bootstrap/ppcx64


goes further (or is it just different as it is a cross-compile?) but gives:

make[1]: Entering directory '/home/me/fpc/trunk/fpcsrc/compiler'
/usr/bin/mkdir -p i386/units/i386-linux
/usr/bin/mkdir -p i386/bin/i386-linux
/home/ctcmw/fpc/trunk/fpcsrc/compiler/ppcross386 -Pi386 -XPi386-linux- 
-Xr -Fui386 -Fusystems -Fu../rtl/units/i386-linux -Fii386 
-FEi386/bin/i386-linux -FUi386/units/i386-linux -n -di386 -dGDB 
-dBROWSERLOG -Fux86 -Sew    -di386 -dGDB -dBROWSERLOG -Fux86 -Sew pp.pas
pp.pas(277,1) Error: Util i386-linux-ld not found, switching to external 
linking

pp.pas(277,1) Fatal: There were 1 errors compiling module, stopping
Fatal: Compilation aborted
make[1]: *** [Makefile:4355: ppc386] Error 1
make[1]: Leaving directory '/home/me/fpc/trunk/fpcsrc/compiler'
make: *** [Makefile:4461: cycle] Error 2

The OS is Fedora 29, and I am reasonably certain a complete set of Gnu 
i386 tools are present.


I will try and generate a backtrace as suggested by Sven later.

Colin



On 23/11/2018 09:52, Pierre Muller wrote:

Hi,

   you should always try to start with a release compiler.

If you have the latest i386 compiler installed start by:

cd fpcsrc/compiler
make distclean cycle OPT="-n" FPC=/path/to/release/ppc386

save the resulting ppc386 on success to /home/me/fpc/bootstrap/ppc386

and then start

make distclean install PREFIX=/home/me/usr FPC=/home/me/fpc/bootstrap/ppc386

If you have no i386 compiler installed,
use your x86_64 release with

cd fpcsrc/compiler
make distclean cycle OS_TARGET=linux CPU_TARGET=i386 OPT="-n" 
FPC=/path/to/release/ppcx64


   Please test this out and report if it solves your problem or not.


Pierre Muller

Le 23/11/2018 à 10:21, C Western a écrit :

I haven't been able to build trunk i386 fpc for a couple of weeks. Is
this supposed to be working, or have I misconfigured something? (I don't
think I have changed anything.) The output is below. I don't think it is
significant, but I am building on a 64 bit system, but with a 32 bit
starting compiler. (The 64 bit build with the 64 bit starting compiler
works fine.)

Colin


make distclean install PREFIX=/home/me/usr FPC=/home/me/fpc/bootstrap/ppc386
()
make[7]: Entering directory '/home/me/fpc/trunk/fpcsrc/rtl'
make -C linux all
make[8]: Entering directory '/home/me/fpc/trunk/fpcsrc/rtl/linux'
/home/me/fpc/trunk/fpcsrc/compiler/ppc1 -Ur -Ur -Xs -O2 -n -Fi../inc
-Fi../i386 -Fi../unix -Fii386 -FE.
-FU/home/me/fpc/trunk/fpcsrc/rtl/units/i386-linux -di386 -dRELEASE -Us
-Sg system.pp
make[8]: *** [Makefile:3912: system.ppu] Segmentation fault (core dumped)
make[8]: Leaving directory '/home/me/fpc/trunk/fpcsrc/rtl/linux'
make[7]: *** [Makefile:2057: linux_all] Error 2
make[7]: Leaving directory '/home/me/fpc/trunk/fpcsrc/rtl'
make[6]: *** [Makefile:4552: rtl] Error 2
make[6]: Leaving directory '/home/me/fpc/trunk/fpcsrc/compiler'
make[5]: *** [Makefile:4403: next] Error 2
make[5]: Leaving directory '/home/me/fpc/trunk/fpcsrc/compiler'
make[4]: *** [Makefile:4413: ppc2] Error 2
make[4]: Leaving directory '/home/me/fpc/trunk/fpcsrc/compiler'
make[3]: *** [Makefile:4422: cycle] Error 2
make[3]: Leaving directory '/home/me/fpc/trunk/fpcsrc/compiler'
make[2]: *** [Makefile:2834: compiler_cycle] Error 2
make[2]: Leaving directory '/home/me/fpc/trunk/fpcsrc'
make[1]: *** [Makefile:2866: build-stamp.i386-linux] Error 2
make[1]: Leaving directory '/home/me/fpc/trunk/fpcsrc'
make: *** [Makefile:2306: fpcsrc/build-stamp.i386-linux] Error 2



___
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal


___
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal



___
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal

Re: [fpc-pascal] Building trunk

2018-11-23 Thread Pierre Muller 
Hi,

  you should always try to start with a release compiler.

If you have the latest i386 compiler installed start by:

cd fpcsrc/compiler
make distclean cycle OPT="-n" FPC=/path/to/release/ppc386

save the resulting ppc386 on success to /home/me/fpc/bootstrap/ppc386

and then start

make distclean install PREFIX=/home/me/usr FPC=/home/me/fpc/bootstrap/ppc386

If you have no i386 compiler installed,
use your x86_64 release with

cd fpcsrc/compiler
make distclean cycle OS_TARGET=linux CPU_TARGET=i386 OPT="-n" 
FPC=/path/to/release/ppcx64


  Please test this out and report if it solves your problem or not.


Pierre Muller

Le 23/11/2018 à 10:21, C Western a écrit :
> I haven't been able to build trunk i386 fpc for a couple of weeks. Is 
> this supposed to be working, or have I misconfigured something? (I don't 
> think I have changed anything.) The output is below. I don't think it is 
> significant, but I am building on a 64 bit system, but with a 32 bit 
> starting compiler. (The 64 bit build with the 64 bit starting compiler 
> works fine.)
> 
> Colin
> 
> 
> make distclean install PREFIX=/home/me/usr FPC=/home/me/fpc/bootstrap/ppc386
> ()
> make[7]: Entering directory '/home/me/fpc/trunk/fpcsrc/rtl'
> make -C linux all
> make[8]: Entering directory '/home/me/fpc/trunk/fpcsrc/rtl/linux'
> /home/me/fpc/trunk/fpcsrc/compiler/ppc1 -Ur -Ur -Xs -O2 -n -Fi../inc 
> -Fi../i386 -Fi../unix -Fii386 -FE. 
> -FU/home/me/fpc/trunk/fpcsrc/rtl/units/i386-linux -di386 -dRELEASE -Us 
> -Sg system.pp
> make[8]: *** [Makefile:3912: system.ppu] Segmentation fault (core dumped)
> make[8]: Leaving directory '/home/me/fpc/trunk/fpcsrc/rtl/linux'
> make[7]: *** [Makefile:2057: linux_all] Error 2
> make[7]: Leaving directory '/home/me/fpc/trunk/fpcsrc/rtl'
> make[6]: *** [Makefile:4552: rtl] Error 2
> make[6]: Leaving directory '/home/me/fpc/trunk/fpcsrc/compiler'
> make[5]: *** [Makefile:4403: next] Error 2
> make[5]: Leaving directory '/home/me/fpc/trunk/fpcsrc/compiler'
> make[4]: *** [Makefile:4413: ppc2] Error 2
> make[4]: Leaving directory '/home/me/fpc/trunk/fpcsrc/compiler'
> make[3]: *** [Makefile:4422: cycle] Error 2
> make[3]: Leaving directory '/home/me/fpc/trunk/fpcsrc/compiler'
> make[2]: *** [Makefile:2834: compiler_cycle] Error 2
> make[2]: Leaving directory '/home/me/fpc/trunk/fpcsrc'
> make[1]: *** [Makefile:2866: build-stamp.i386-linux] Error 2
> make[1]: Leaving directory '/home/me/fpc/trunk/fpcsrc'
> make: *** [Makefile:2306: fpcsrc/build-stamp.i386-linux] Error 2
> 
> 
> 
> ___
> fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
> http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal
> 
___
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal

Re: [fpc-pascal] Building trunk

2018-11-23 Thread Sven Barth via fpc-pascal 
Am Fr., 23. Nov. 2018, 10:26 hat C Western  geschrieben:

> I haven't been able to build trunk i386 fpc for a couple of weeks. Is
> this supposed to be working, or have I misconfigured something? (I don't
> think I have changed anything.) The output is below. I don't think it is
> significant, but I am building on a 64 bit system, but with a 32 bit
> starting compiler. (The 64 bit build with the 64 bit starting compiler
> works fine.)
>

We have i386 trunk building on at least one x86_64-linux machine, so it
can't be a principal problem. :/
Could you check whether it's FPC itself that segfaults or something else
and if the former try to retrieve a stacktrace, please?

Regards,
Sven

>
___
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal

[fpc-pascal] Building trunk

2018-11-23 Thread C Western 
I haven't been able to build trunk i386 fpc for a couple of weeks. Is 
this supposed to be working, or have I misconfigured something? (I don't 
think I have changed anything.) The output is below. I don't think it is 
significant, but I am building on a 64 bit system, but with a 32 bit 
starting compiler. (The 64 bit build with the 64 bit starting compiler 
works fine.)


Colin


make distclean install PREFIX=/home/me/usr FPC=/home/me/fpc/bootstrap/ppc386
()
make[7]: Entering directory '/home/me/fpc/trunk/fpcsrc/rtl'
make -C linux all
make[8]: Entering directory '/home/me/fpc/trunk/fpcsrc/rtl/linux'
/home/me/fpc/trunk/fpcsrc/compiler/ppc1 -Ur -Ur -Xs -O2 -n -Fi../inc 
-Fi../i386 -Fi../unix -Fii386 -FE. 
-FU/home/me/fpc/trunk/fpcsrc/rtl/units/i386-linux -di386 -dRELEASE -Us 
-Sg system.pp

make[8]: *** [Makefile:3912: system.ppu] Segmentation fault (core dumped)
make[8]: Leaving directory '/home/me/fpc/trunk/fpcsrc/rtl/linux'
make[7]: *** [Makefile:2057: linux_all] Error 2
make[7]: Leaving directory '/home/me/fpc/trunk/fpcsrc/rtl'
make[6]: *** [Makefile:4552: rtl] Error 2
make[6]: Leaving directory '/home/me/fpc/trunk/fpcsrc/compiler'
make[5]: *** [Makefile:4403: next] Error 2
make[5]: Leaving directory '/home/me/fpc/trunk/fpcsrc/compiler'
make[4]: *** [Makefile:4413: ppc2] Error 2
make[4]: Leaving directory '/home/me/fpc/trunk/fpcsrc/compiler'
make[3]: *** [Makefile:4422: cycle] Error 2
make[3]: Leaving directory '/home/me/fpc/trunk/fpcsrc/compiler'
make[2]: *** [Makefile:2834: compiler_cycle] Error 2
make[2]: Leaving directory '/home/me/fpc/trunk/fpcsrc'
make[1]: *** [Makefile:2866: build-stamp.i386-linux] Error 2
make[1]: Leaving directory '/home/me/fpc/trunk/fpcsrc'
make: *** [Makefile:2306: fpcsrc/build-stamp.i386-linux] Error 2



___
fpc-pascal maillist  -  fpc-pascal@lists.freepascal.org
http://lists.freepascal.org/cgi-bin/mailman/listinfo/fpc-pascal