[kde-freebsd] after compiling x11/kde4 problems with /usr/local/bin/startkde (SOLVED)

[Matthias Apitz]

El día Sunday, November 01, 2009 a las 10:32:24AM +0000, Robert Watson escribió:

> 
> On Sun, 1 Nov 2009, Matthias Apitz wrote:
> 
> >>i.e. it brings up this xmessage box and in the log files I can see that 
> >>'start_kdeinit_wrapper' SIGABORT's. The KDE desktop itself comes up fine. 
> >>This is, as I said, after compiling the port x11/kde4. The file 
> >>/usr/local/bin/start_kdeinit_wrapper is not touched by the port x11/kde4 
> >>and neither the shared libs it is depending:
> >>
> >>$ ldd /usr/local/bin/start_kdeinit_wrapper
> >>/usr/local/bin/start_kdeinit_wrapper:
> >>        libjpeg.so.10 => /usr/local/lib/libjpeg.so.10 (0x2808e000)
> >>        libc.so.7 => /lib/libc.so.7 (0x280c2000)
> 
> Could you show us readelf -l /usr/local/bin/start_kdeinit_wrapper

Here we go:

$ readelf -l /usr/local/bin/start_kdeinit_wrapper

Elf file type is EXEC (Executable file)
Entry point 0x8048480
There are 6 program headers, starting at offset 52

Program Headers:
  Type           Offset   VirtAddr   PhysAddr   FileSiz MemSiz  Flg Align
  PHDR           0x000034 0x08048034 0x08048034 0x000c0 0x000c0 R E 0x4
  INTERP         0x0000f4 0x080480f4 0x080480f4 0x00015 0x00015 R   0x1
      [Requesting program interpreter: /libexec/ld-elf.so.1]
  LOAD           0x000000 0x08048000 0x08048000 0x006a8 0x006a8 R E 0x1000
  LOAD           0x0006a8 0x080496a8 0x080496a8 0x00104 0x0010c RW 0x1000
  DYNAMIC        0x0006b8 0x080496b8 0x080496b8 0x000c0 0x000c0 RW  0x4
  NOTE           0x00010c 0x0804810c 0x0804810c 0x00018 0x00018 R   0x4

 Section to Segment mapping:
  Segment Sections...
   00     
   01     .interp 
   02     .interp .note.ABI-tag .hash .dynsym .dynstr .gnu.version .gnu.version_ r .rel.plt .init .plt .text .fini .rodata 
   03     .data .eh_frame .dynamic .ctors .dtors .jcr .got .bss 
   04     .dynamic 
   05     .note.ABI-tag 

> >it does not abort when you set
> >
> ># sysctl security.bsd.map_at_zero=1
> >security.bsd.map_at_zero: 0 -> 1
> >
> >I think that security.bsd.map_at_zero was already 0 before compiling 
> >x11/kde4, i.e. no part of KDE4 changed this sysctl value; so it remains 
> >open, what caused this effect, but at least it is working again;
> 
> Could you confirm you are running with a userspace/kernel of at least 
> r198203 (the date of the last PIE-related fix following a move to 
> disallowing NULL mappings).

NAK, userland and kernel is:

$ uname -a
FreeBSD vm-azul.Sisis.de 9.0-CURRENT FreeBSD 9.0-CURRENT #0 r197801: Mon Oct 12 13:33:32 CEST 2009
guru at vm-azul.Sisis.de:/usr/obj/usr/src/sys/GENERIC  i386

Thx

	matthias
-- 
Matthias Apitz
t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211
e <guru at unixarea.de> - w http://www.unixarea.de/
Vote NO to EU The Lisbon Treaty: http://www.no-means-no.eu