Tested on the XPS machine with the free "ati" driver
http://www.penlug.org/twiki/bin/view/Main/LinuxHardwareInfoDellDimensionXPS
http://www.penlug.org/twiki/bin/view/Main/LinuxHardwareInfoATIRadeonX800
running the Live CD of hardy-desktop-i386.iso (the January 2008 one with
18b9db3935b2910e4af
Tested that this bug also reproduces in Gutsy x86 when running compiz-fusion
with the open-source "ati" driver
Section "Device"
Identifier "ATI Technologies Inc R423 UK [Radeon X800SE (PCIE)]"
Driver "ati"
BusID "PCI:1:0:0"
EndSection
This is on a
Tested that this bug also reproduces in Gutsy x86 when running compiz-fusion
with the
open-source i810 driver, on a HP/Compaq dc7600 desktop.
As on x86_64, rebuilding xterm on x86 from source with debug symbols is a
workaround (problem doesn't occur):
sudo apt-get install libxaw-headers libxa
Tested that this bug also reproduces in Gutsy on x86 (not only on x86_64) when
running compiz-fusion with the nVidia drivers (running Gutsy on a Dell box
http://www.penlug.org/twiki/bin/view/Main/LinuxHardwareInfoDellDimensionXPS
with an nVidia 5200 card:
http://www.penlug.org/twiki/bin/view/M
After installing libxt6-dbg (apt-get install libxt6-dbg) and running
under gdb, it gives:
$ gdb /usr/bin/xterm
GNU gdb 6.6-debian
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute co
On Tue, Dec 18, 2007 at 18:01:15 -, PeterKnaggs wrote:
> The stack trace from "gdb /usr/bin/xterm" (i.e. without debug symbols)
> and doing "run" over and over again until the problem reproduces is:
>
> (no debugging symbols found)
>
> Program received signal SIGSEGV, Segmentation fault.
> [
Strangely, when running "valgrind /usr/bin/xterm" it gives:
valgrind: /usr/bin/xterm: Permission denied
Whereas when running "valdrind ~/xterm-229/xterm" (i.e. on the one I built from
the sources) gives:
==8270== Memcheck, a memory error detector.
==8270== Copyright (C) 2002-2007, and GNU GPL'd
The bug doesn't appear to be in xterm, because disabling compiz-fusion
by adding the following line:
export WINDOW_MANAGER=metacity
to $HOME/.gnomerc
causes the bug to no longer occur.
The stack trace from "gdb /usr/bin/xterm" (i.e. without debug symbols)
and doing "run" over and over again unt
Ah, sorry. I added "-lncurses" to the end of the link line, and now
xterm links OK using:
gcc -g -O2 -o xterm button.o cachedGCs.o charproc.o charsets.o \
cursor.o data.o doublechr.o fontutils.o input.o main.o menu.o misc.o \
print.o ptydata.o screen.o scrollbar.o tabs.o util.o xstrings.o xtermc
sudo apt-get install libxaw-headers libxaw7-dev libncurses5-dev
$ apt-get source xterm
Reading package lists... Done
Building dependency tree
Reading state information... Done
Need to get 904kB of source archives.
Get:1 http://us.archive.ubuntu.com gutsy/main xterm 229-1 (dsc) [805B]
Get:2
On Fri, Dec 14, 2007 at 16:59:28 -, PeterKnaggs wrote:
> Adding an attachment.
>
> Place this file in your $HOME to reproduce the problem:
>
> $ xterm &
> [2] 7210
> $ xterm &
> [3] 7227
> $ xterm &
> [4] 7244
> $ xterm &
> [5] 7245
> [4] Segmentation fault xterm
Please rebuild xterm
The problem doesn't occur (using the same configuration file) using
Ubuntu Gutsy 7.10 on x86 machines, it seems to occur only on x86_64.
--
xterm on x86_64 intermittently segfaults when ~/XTerm contains "*scrollBar:
true" and "*saveLines: 10"
https://bugs.launchpad.net/bugs/176393
You recei
The problem didn't occur on Ubuntu Feisty Fawn on x86_64 (I had been previously
using
the same configuration file on the iMac machine when it was running Feisty
Fawn, although
I no longer have that environment available any more as the machine is running
Gutsy now).
--
xterm on x86_64 intermit
Adding an attachment.
Place this file in your $HOME to reproduce the problem:
$ xterm &
[2] 7210
$ xterm &
[3] 7227
$ xterm &
[4] 7244
$ xterm &
[5] 7245
[4] Segmentation fault xterm
$ xterm &
[6] 7262
$ xterm &
[7] 7279
[1] Donexterm
[2] Donexte
14 matches
Mail list logo
