Bug#255772: marked as done (libxaw7: xterm dies with segfault)
Your message dated Thu, 8 Jul 2004 16:36:16 -0500
with message-id <20040708213616.GK6275@redwald.deadbeast.net>
and subject line Bug#255772: libxaw7: xterm dies with segfault
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 22 Jun 2004 23:07:50 +0000
>From mn@mn.com.ua Tue Jun 22 16:07:50 2004
Return-path: <mn@mn.com.ua>
Received: from sled.volia.net (mail.voliacable.com) [82.144.192.38]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1BcuMo-0002hY-00; Tue, 22 Jun 2004 16:07:50 -0700
Received: from tabernacle.mn.home (ip.82.144.215.173.dyn.pool-1.broadband.voliacable.com [82.144.215.173])
by mail.voliacable.com (8.12.9/8.12.9) with ESMTP id i5MN7ijU020575
for <submit@bugs.debian.org>; Wed, 23 Jun 2004 02:07:45 +0300 (EEST)
Received: by tabernacle.mn.home (Postfix, from userid 1000)
id 4E6142581; Wed, 23 Jun 2004 02:07:42 +0300 (EEST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: "Mykola A. Nickishov" <mn@mn.com.ua>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: libxaw7: xterm dies with segfault
X-Mailer: reportbug 2.61
Date: Wed, 23 Jun 2004 02:07:42 +0300
Message-Id: <20040622230742.4E6142581@tabernacle.mn.home>
Delivered-To: submit@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level:
Package: libxaw7
Version: 4.3.0.dfsg.1-5
Severity: normal
xterm 4.3.0.dfsg.1-5 dies with SIGSEGV:
mn@tabernacle:~$ gdb xterm
(gdb) run
Starting program: /usr/X11R6/bin/xterm
(no debugging symbols found)...(no debugging symbols found)...
Program received signal SIGSEGV, Segmentation fault.
0x40146af0 in XawTreeForceLayout () from /usr/X11R6/lib/libXaw.so.7
(gdb)
After downgrading libxaw7 to 4.3.0.dfsg.1-4 problem has gone.
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.6-2-k7
Locale: LANG=uk_UA.UTF-8, LC_CTYPE=uk_UA.UTF-8
Versions of packages libxaw7 depends on:
ii libc6 2.3.2.ds1-13 GNU C Library: Shared libraries an
ii libice6 4.3.0.dfsg.1-5 Inter-Client Exchange library
ii libsm6 4.3.0.dfsg.1-5 X Window System Session Management
ii libxext6 4.3.0.dfsg.1-5 X Window System miscellaneous exte
ii libxmu6 4.3.0.dfsg.1-5 X Window System miscellaneous util
ii libxpm4 4.3.0.dfsg.1-5 X pixmap library
ii libxt6 4.3.0.dfsg.1-5 X Toolkit Intrinsics
ii xlibs 4.3.0.dfsg.1-5 X Window System client libraries m
-- no debconf information
---------------------------------------
Received: (at 255772-done) by bugs.debian.org; 8 Jul 2004 21:36:17 +0000
>From branden@redwald.deadbeast.net Thu Jul 08 14:36:17 2004
Return-path: <branden@redwald.deadbeast.net>
Received: from dhcp065-026-182-085.indy.rr.com (localhost) [65.26.182.85]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1BigYz-0004hN-00; Thu, 08 Jul 2004 14:36:17 -0700
Received: by localhost (Postfix, from userid 1000)
id B4DFC68C047; Thu, 8 Jul 2004 16:36:16 -0500 (EST)
Date: Thu, 8 Jul 2004 16:36:16 -0500
From: Branden Robinson <branden@debian.org>
To: 255772-done@bugs.debian.org
Subject: Re: Bug#255772: libxaw7: xterm dies with segfault
Message-ID: <20040708213616.GK6275@redwald.deadbeast.net>
References: <20040622230742.4E6142581@tabernacle.mn.home>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="h1Kgj0J7YauQlxie"
Content-Disposition: inline
In-Reply-To: <20040622230742.4E6142581@tabernacle.mn.home>
Mail-Copies-To: nobody
X-No-CC: I subscribe to this list; do not CC me on replies.
User-Agent: Mutt/1.5.6+20040523i
Delivered-To: 255772-done@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-3.1 required=4.0 tests=BAYES_44,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level:
--h1Kgj0J7YauQlxie
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Wed, Jun 23, 2004 at 02:07:42AM +0300, Mykola A. Nickishov wrote:
> Package: libxaw7
> Version: 4.3.0.dfsg.1-5
> Severity: normal
>=20
> xterm 4.3.0.dfsg.1-5 dies with SIGSEGV:
>=20
> mn@tabernacle:~$ gdb xterm
> (gdb) run
> Starting program: /usr/X11R6/bin/xterm
> (no debugging symbols found)...(no debugging symbols found)...
> Program received signal SIGSEGV, Segmentation fault.
> 0x40146af0 in XawTreeForceLayout () from /usr/X11R6/lib/libXaw.so.7
> (gdb)
>=20
> After downgrading libxaw7 to 4.3.0.dfsg.1-4 problem has gone.
Closing this as a duplicate of #255749, filed by the same submitter, and
with the same information as above in the bug logs.
[The following is a form letter.]
Hello,
You recently filed a duplicate bug report against a Debian package; that
is, the problem had already been reported.
While there is often nothing inherently wrong with doing so, the filing of
duplicate reports can cause Debian package maintainers to spend time
performing triage and maintenance operations on bug reports (e.g.,
instructing the Debian Bug Tracking System to merge the duplicates) that
could otherwise be spent resolving problems and doing other work on the
package.
One very good way to file bugs with the Debian Bug Tracking System is to
use the "reportbug" package and command of the same name. A very nice
feature of reportbug is that, if the machine where you run it has network
access to the World Wide Web, it can query the Debian Bug Tracking System
and show you existing reports. This reduces the chance that you'll file a
duplicate report, and offers you the option of adding follow-up information
to an existing bug report. This is especially valuable if you have unique
information to add to an existing report, because this way information
relevant to the problem is gathered together in one place as opposed to
being scattered among multiple, duplicate bug reports where some facts may
be overlooked by the package maintainers. The reportbug program also does
a lot of automatic information-gathering that helps package maintainers to
understand your system configuration, and also ensures that your message to
the Debian Bug Tracking System is well-formed so that it is processed
correctly by the automated tools that manage the reports. (If you've ever
gotten a "bounce" message from the Debian Bug Tracking System that tells
you your message couldn't be processed, you might appreciate this latter
feature.)
Therefore, I strongly urge you to give "reportbug" a try as your primary
bug reporting tool for the Debian System. (If you already do use
"reportbug", please see below.)
One way to install reportbug is with "apt-get"; for
example:
# apt-get install reportbug
The "reportbug" command has a few different modes that cater to different
levels of user expertise. If this message has contained a lot of jargon
that is unfamiliar to you, you likely want to use reportbug's "novice"
mode; here's one way to do that.
$ reportbug --mode=3Dnovice
Please enter the name of the package in which you have found a problem,
or type 'other' to report a more general problem.
>
If you're more sophisticated, or if you are not using the released version
of Debian ("stable"), but instead Debian "testing" or "unstable", you
should use reportbug's standard mode.
$ reportbug
Please enter the name of the package in which you have found a problem,
or type 'other' to report a more general problem.
>
The reportbug command is extensively documented in its usage message and
manual page. Commands to view these pieces of documentation are:
$ reportbug --help | more
$ man reportbug
(The output of the above commands has been omitted from this message.)
If you do use reportbug, but are so daunted by the large number of bugs
already filed against a package that you feel you cannot search for a
duplicate, please note that reportbug has a (f)ilter feature that enables
you to use a keyword search to limit the number of bugs reported. (If
you're feeling ambitious, the filter feature also accepts a regular
expression.) For example, if you'd like to report a SEGV (segfault), you
might filter based on the term "SEGV". If you're having trouble upgrading
a package, you might filter based on "upgrad" (to catch both "upgrade" and
"upgrading"). Some package maintainers retitle bugs to contain keywords so
as to facilitate better filtering and convey more useful information, since
a bug report with a title of "broken" or the like is not very useful to
anyone.
We appreciate you taking the time to help package maintainers serve you
better by reducing the amount of time they need to spend coping with
duplicate bug reports.
Thanks for using the Debian system!
--=20
G. Branden Robinson | Religion is excellent stuff for
Debian GNU/Linux | keeping common people quiet.
branden@debian.org | -- Napoleon Bonaparte
http://people.debian.org/~branden/ |
--h1Kgj0J7YauQlxie
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iEYEARECAAYFAkDtvlAACgkQ6kxmHytGonzIZQCgi/Yr3QNuGFTzw/s3GOB4s8cR
aX8AnjSA4l920uncGIAfG0QGkeYMCdvv
=j/JU
-----END PGP SIGNATURE-----
--h1Kgj0J7YauQlxie--
Reply to: