Recent

Author Topic: FreeBSD 9.1-RELEASE, segment fault  (Read 4969 times)

MrAnon

  • Newbie
  • Posts: 2
FreeBSD 9.1-RELEASE, segment fault
« on: March 19, 2013, 02:59:52 am »
Hello all,

I can't seem to get Lazarus to start. I have tried the ports version of lazarus (lazarus-0.9.30) and the svn version (revision 40588); they both compile without errors. I have also tried using FPC 2.6.0 and the newer 2.6.2 version. When starting from the terminal it simply says 'TRasterImage.BitmapHandleNeeded: Unable to create handles, using default.'

Using gdb is shows:

[New LWP 136660]
[New Thread 29c04300 (LWP 136660/lazarus)]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 29c04300 (LWP 136660/lazarus)]
$2936aa36 in _malloc_prefork () from /lib/libc.so.7

I've installed Lazarus inside a VM of PC-BSD 9.1 and also FreeBSD 9.1, and Lazarus started fine, so I redid the same procedure I used on the FreeBSD VM but haven't had any success. I normally use the tiling window manager Musca, but installed Xfce4 to rule out a wm issue.

Here is some additional information:

$ uname -a
FreeBSD 9.1-RELEASE FreeBSD 9.1-RELEASE #0 r245090: Mon Jan  7 18:22:03 EST 2013   :/usr/obj/usr/src/sys/GENERIC  i386

$ portmaster -l | grep gtk       
gtk-1.2.10_22
gtk-2.24.17

$ portmaster -l | grep nvidia
nvidia-driver-310.32


Any help would be appreciated, thank you.

Graeme

  • Hero Member
  • *****
  • Posts: 1430
    • Graeme on the web
Re: FreeBSD 9.1-RELEASE, segment fault
« Reply #1 on: March 19, 2013, 10:23:12 am »
Unfortunately I don't have any advice, but I can say that Lazarus 1.1 (trunk) runs without problems here on my 64-bit FreeBSD 9.1 system. I have first used FPC 2.6.0, and about a week ago upgraded to FPC 2.6.2.

I haven't used the ports collection for them. Lazarus I downloaded via the Git repository, and FPC I installed via the binary release files from SourceForge.

I use JWM (Joe's Window Manager) with X11, and the accelerated Intel driver. The VESA driver works fine too.

I can suggest to recompile the whole Lazarus with the -gl compiler parameter. Then run it via GDB again. Once it crashed, do a back trace, which will give you a much more detailed backtrace. See the Free Pascal Wiki if you don't know how to create a backtrace in GDB.
--
fpGUI Toolkit - a cross-platform GUI toolkit using Free Pascal
http://fpgui.sourceforge.net/

marcov

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 8599
  • FPC developer.
Re: FreeBSD 9.1-RELEASE, segment fault
« Reply #2 on: March 19, 2013, 11:07:40 am »
Do you see the TRasterImage error? Might point to some X problem?

Graeme

  • Hero Member
  • *****
  • Posts: 1430
    • Graeme on the web
Re: FreeBSD 9.1-RELEASE, segment fault
« Reply #3 on: March 19, 2013, 05:57:21 pm »
No, I have never seen that error here.
--
fpGUI Toolkit - a cross-platform GUI toolkit using Free Pascal
http://fpgui.sourceforge.net/

MrAnon

  • Newbie
  • Posts: 2
Re: FreeBSD 9.1-RELEASE, segment fault
« Reply #4 on: March 20, 2013, 01:59:32 am »
Here are three backtraces, the first from a revision I grabbed yesterday, the second is Lazarus from the ports tree, and the third after I reinstalled some ports.

(revision 40588) - http://pastebin.com/4Hz4130Y

(Ports - Lazarus-1.0.4) - http://pastebin.com/AStSvNcL

Below is a list of ports I reinstalled; my ports tree is up to date.

devel/glib20
graphics/gdk-pixbuf2
x11/libX11
x11/xorg-minimal
x11-servers/xorg-server
x11-toolkits/gtk20

Here is the backtrace after I reinstalled the above ports (this is using the ports version of Lazarus) - http://pastebin.com/KbYwT9vR

Although the backtrace is different, I still get the 'TRasterImage.BitmapHandleNeeded: Unable to create handles, using default' message when starting Lazarus from the terminal.

marcov

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 8599
  • FPC developer.
Re: FreeBSD 9.1-RELEASE, segment fault
« Reply #5 on: March 20, 2013, 10:42:07 am »
I had a look at your tracebacks, and I have a very initial and rough theory:

Seems that gdk_pixbuf_new_from_data is the problem. From googling a bit I get the impression that that can happen if the relevant gdk (cairo) parts don't support the relevant image format.

So either the relevant GTK/GDK/Cairo whatever was compiled without some file supports, or it tries to load certain pacakges (libxpm/libpng/libjpg etc) dynamically, and it can't find it.

This might be from your compiling by hand, and/or the ports tree only enabling imageformats that are installed or so.

 

TinyPortal © 2005-2018