DragonFly kernel List (threaded) for 2009-09
DragonFly BSD
DragonFly kernel List (threaded) for 2009-09
[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]

Re: Signal 11 and the amd64 port


From: Jordan Gordeev <jgordeev@xxxxxx>
Date: Mon, 21 Sep 2009 22:37:54 +0300

Francois Tigeot wrote:

I just installed a new DragonFly/amd64 system on a blank disk. Most of the
basic applications (base system, non-graphic packages) work fine.

While building applications from pkgsrc, I noticed many crashes of make(1)
with signal 11s. Nevertheless, I was able to install most of the programs I
wanted.

Things took a turn for the worse when I tried to run X11. None of the window
managers I tested could run. They all crashed with signal 11s.
The only application I was able to run under X is xterm. All others I could
test crashed immediately after launch.

I don't believe the new amd64 port should be so unstable. My test machine is
a Core 2 Duo system and runs DragonFly/i386 perfectly fine.

What can I do to find out what's wrong with X11 applications ?



X support for the amd64 port was added just a few days ago and nobody has put the effort yet to make it work well.
From my very limited testing, xdm and twm seem to work, while e16 crashes.
What can you do? You can compile everything with debugging information and obtain core files of the crashing apps. Then you can (try to) analyse the core files with gdb.
To compile the base system with full debugging information you put the following in /etc/make.conf:
CFLAGS+=-g
STRIP=
To build pkgsrc packages with full debugging information you put the following into /usr/pkg/etc/mk.conf:
CFLAGS+=-g
INSTALL_UNSTRIPPED=yes
You can also use ktrace in your debugging.





[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]