Bug#356586: xpdf segfault on amd64
On Mon, 13 Mar 2006, Hamish Moffatt wrote: It can't be a general amd64 problem as I'm running amd64 myself and using Xpdf regularly. Oh boy, now I feel silly because I left out an important detail. I could have sworn I stated it in my original message, but this occurs when X-forwarded over ssh and not locally. -- D. Hilley ([EMAIL PROTECTED]) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#356586: xpdf segfault on amd64
On Sat, Mar 25, 2006 at 06:52:51PM -0500, D. Hilley wrote: On Mon, 13 Mar 2006, Hamish Moffatt wrote: It can't be a general amd64 problem as I'm running amd64 myself and using Xpdf regularly. Oh boy, now I feel silly because I left out an important detail. I could have sworn I stated it in my original message, but this occurs when X-forwarded over ssh and not locally. Interesting. So is your X server 32-bit or 64-bit? So you are sshing TO the amd64 machine, from what other machine? I'm running a 64-bit Xserver. I tried ssh from 64-bit to localhost, and from 32-bit emulation to localhost, and that all worked ok. I haven't tried from another machine with 32-bit X server yet though. Thanks, Hamish -- Hamish Moffatt VK3SB [EMAIL PROTECTED] [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#356586: xpdf segfault on amd64
On Sun, 26 Mar 2006, Hamish Moffatt wrote: Interesting. So is your X server 32-bit or 64-bit? So you are sshing TO the amd64 machine, from what other machine? The other machine is a up-to-date 32-bit Debian testing/unstable machine. There is no problem with running xpdf X-forwarded in the other direction (from 32-bit forwarded to 64-bit). What system info do you need about the other machine? Here's some basic info: -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (990, 'testing'), (500, 'stable'), (50, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.9-ac11 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages xpdf depends on: ii xpdf-common 3.01-7 Portable Document Format ii xpdf-reader 3.01-7 Portable Document Format ii xpdf-utils3.01-7 Portable Document Format xpdf recommends no packages. Versions of packages xpdf-reader depends on: ii gsfonts 8.14+v8.11+urw-0.2 Fonts for the Ghostscript ii lesstif2 1:0.94.4-1.1 OSF/Motif 2.1 implementation ii libc6 2.3.6-3GNU C Library: Shared ii libfreetype6 2.1.10-1 FreeType 2 font engine, ii libgcc1 1:4.0.3-1 GCC support library ii libice6 6.9.0.dfsg.1-4 Inter-Client Exchange library ii libpaper1 1.1.14-5 Library for handling paper ii libsm66.9.0.dfsg.1-4 X Window System Session ii libstdc++64.0.3-1The GNU Standard C++ Library ii libt1-5 5.1.0-2Type 1 font rasterizer ii libx11-6 6.9.0.dfsg.1-4 X Window System protocol ii libxext6 6.9.0.dfsg.1-4 X Window System miscellaneous ii libxp66.9.0.dfsg.1-4 X Window System printing ii libxpm4 6.9.0.dfsg.1-4 X pixmap library ii libxt66.9.0.dfsg.1-4 X Toolkit Intrinsics ii xpdf-common 3.01-7 Portable Document Format ii zlib1g1:1.2.3-9 compression library - runtime -- D. Hilley ([EMAIL PROTECTED]) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#356586: xpdf segfault on amd64
Subject: xpdf segfault on amd64 Package: xpdf-reader Version: 3.01-7 Severity: important Hi, I'm running testing/unstable amd64 debian and xpdf segfaults for me every time at startup. I'm not sure if this is actually an xpdf bug or perhaps in some X library. I saw a post on the linux.debian.ports.x86-64 from August 25th 2005 which is the exact same problem (title: xpdf segmentation fault from: Karl Hoppel). $ xpdf Segmentation fault Here's gdb's output: $ gdb /usr/bin/xpdf.bin Program received signal SIGSEGV, Segmentation fault. 0x2c0d6c4b in memcpy () from /lib/libc.so.6 (gdb) where #0 0x2c0d6c4b in memcpy () from /lib/libc.so.6 #1 0x2b032ec0 in _XmReadDragBuffer () from /usr/lib/libXm.so.2 #2 0x2b03421e in _XmByteOrder () from /usr/lib/libXm.so.2 #3 0x2b034703 in _XmInitTargetsTable () from /usr/lib/libXm.so.2 #4 0x2b034bf9 in _XmTargetsToIndex () from /usr/lib/libXm.so.2 #5 0x2b03f66a in _XmICCEventToICCCallback () from /usr/lib/libXm.so.2 #6 0x2b0a28e5 in XmTextFieldXYToPos () from /usr/lib/libXm.so.2 #7 0x2b252019 in XtInitializeWidgetClass () from /usr/X11R6/lib/libXt.so.6 #8 0x2b252561 in XtInitializeWidgetClass () from /usr/X11R6/lib/libXt.so.6 #9 0x2b252a21 in _XtCreateWidget () from /usr/X11R6/lib/libXt.so.6 #10 0x2b252c96 in XtCreateWidget () from /usr/X11R6/lib/libXt.so.6 #11 0x2b09b663 in XmCreateTextField () from /usr/lib/libXm.so.2 #12 0x004894f8 in ?? () #13 0x0048af71 in ?? () #14 0x00480659 in ?? () #15 0x0048e8ff in ?? () #16 0x2c07e4ca in __libc_start_main () from /lib/libc.so.6 #17 0x00405efa in ?? () #18 0x7faded78 in ?? () #19 0x2abc29c0 in ?? () from /lib64/ld-linux-x86-64.so.2 #20 0x0001 in ?? () #21 0x7fae0bca in ?? () #22 0x in ?? () I can also provide strace output if that would help. $ uname -a Linux rustbucket 2.6.15-rc6 #1 SMP PREEMPT Wed Dec 21 20:51:34 EST 2005 x86_64 GNU/Linux -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-rc6 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages xpdf depends on: ii xpdf-common 3.01-7 Portable Document Format (PDF) sui ii xpdf-reader 3.01-7 Portable Document Format (PDF) sui ii xpdf-utils3.01-7 Portable Document Format (PDF) sui xpdf recommends no packages. Versions of packages xpdf-reader depends on: ii gsfonts 8.14+v8.11+urw-0.2 Fonts for the Ghostscript interpre ii lesstif2 1:0.94.4-1.1 OSF/Motif 2.1 implementation relea ii libc6 2.3.5-13 GNU C Library: Shared libraries an ii libfreetype6 2.1.10-1 FreeType 2 font engine, shared lib ii libgcc1 1:4.0.2-9 GCC support library ii libice6 6.9.0.dfsg.1-4 Inter-Client Exchange library ii libpaper1 1.1.14-5 Library for handling paper charact ii libsm66.9.0.dfsg.1-4 X Window System Session Management ii libstdc++64.0.2-9The GNU Standard C++ Library v3 ii libt1-5 5.1.0-2Type 1 font rasterizer library - r ii libx11-6 6.9.0.dfsg.1-4 X Window System protocol client li ii libxext6 6.9.0.dfsg.1-4 X Window System miscellaneous exte ii libxp66.9.0.dfsg.1-4 X Window System printing extension ii libxpm4 6.9.0.dfsg.1-4 X pixmap library ii libxt66.9.0.dfsg.1-4 X Toolkit Intrinsics ii xpdf-common 3.01-7 Portable Document Format (PDF) sui ii zlib1g1:1.2.3-9 compression library - runtime -- no debconf information -- D. Hilley ([EMAIL PROTECTED]) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#356586: xpdf segfault on amd64
On Sun, Mar 12, 2006 at 04:46:14PM -0500, D. Hilley wrote: Subject: xpdf segfault on amd64 Package: xpdf-reader Version: 3.01-7 Severity: important Hi, I'm running testing/unstable amd64 debian and xpdf segfaults for me every time at startup. I'm not sure if this is actually an xpdf bug or perhaps in some X library. I saw a post on the linux.debian.ports.x86-64 from August 25th 2005 which is the exact same problem (title: xpdf segmentation fault from: Karl Hoppel). [..] It can't be a general amd64 problem as I'm running amd64 myself and using Xpdf regularly. Perhaps it's a break with a recent library upgrade; I'll upgrade asap and see how it goes. I can also provide strace output if that would help. Yes that couldn't hurt. ii lesstif2 1:0.94.4-1.1 OSF/Motif 2.1 implementation relea ii libfreetype6 2.1.10-1 FreeType 2 font engine, shared lib ii libgcc1 1:4.0.2-9 GCC support library ii libice6 6.9.0.dfsg.1-4 Inter-Client Exchange library [and others] These are the same for me; ii libc6 2.3.5-13 GNU C Library: Shared libraries an I have 2.3.6-1. Can you try upgrading? Seems unlikely to be the cause though. Hamish -- Hamish Moffatt VK3SB [EMAIL PROTECTED] [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
