Your message dated Sun, 20 Nov 2005 11:32:10 -0800
with message-id <[EMAIL PROTECTED]>
and subject line Bug#306267: fixed in gdb 6.3.90.20051119-1
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; 25 Apr 2005 11:33:57 +0000
>From [EMAIL PROTECTED] Mon Apr 25 04:33:57 2005
Return-path: <[EMAIL PROTECTED]>
Received: from zigzag.lvk.cs.msu.su [158.250.17.23]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1DQ1qf-00037r-00; Mon, 25 Apr 2005 04:33:57 -0700
Received: from ghost by zigzag.lvk.cs.msu.su with local (Exim 4.50)
id 1DQ1qc-00044T-EW
for [EMAIL PROTECTED]; Mon, 25 Apr 2005 15:33:54 +0400
Content-Type: multipart/mixed; boundary="===============1317802100=="
MIME-Version: 1.0
From: Vladimir Prus <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: gdb: Gdb gets SITTOU when printing "Pending breakpoint resolved"
message
X-Mailer: reportbug 3.8
Date: Mon, 25 Apr 2005 15:33:54 +0400
Message-Id: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(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_2005_01_02
X-Spam-Level:
This is a multi-part MIME message sent by reportbug.
--===============1317802100==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Package: gdb
Version: 6.3-5
Severity: normal
Tags: patch
When terminal options include 'tostop' (stop on output from non-foreground
process), which is set when running under Midnight Commander, gdb gets
SIGTTOU and stops when pending breakpoint is resolved.
Here's my session:
(gdb) b localize.cpp:54
No source file named localize.cpp.
Make breakpoint pending on future shared library load? (y or [n]) y
Breakpoint 1 (localize.cpp:54) pending.
(gdb) r
Starting program: /home/ghost/Work/llvm/Debug/bin/opt -globalsmodref-aa -load
/home/ghost/Work/Research/Implementation/llvm_feasibility/localize.so -localize
a.bc -o a_l.bc -f
[1]+ Stopped gdb opt
After I "run fg", the output is:
Breakpoint 2 at 0xb7fe482b: file localize.cpp, line 54.
Pending breakpoint "localize.cpp:54" resolved
After I exchange the lines:
target_terminal_inferior ();
re_enable_breakpoints_in_shlibs ();
in infrun.c (line 2121), gdb works as expected. The problem is that
're_enable_breakpoints_in_shlibs' prints the 'Pending breakpoint resolved"
message, while gdb does not own the terminal.
-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (620, 'testing'), (600, 'unstable'), (550, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.11-1-zigzag
Locale: LANG=C, LC_CTYPE=ru_RU.KOI8-R (charmap=KOI8-R)
Versions of packages gdb depends on:
ii libc6 2.3.2.ds1-20 GNU C Library: Shared libraries an
ii libncurses5 5.4-4 Shared libraries for terminal hand
ii libreadline4 4.3-11 GNU readline and history libraries
-- no debconf information
--===============1317802100==
Content-Type: text/x-c; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="infrun.diff"
--- infrun.c.orig 2005-04-25 15:22:41.000000000 +0400
+++ infrun.c 2005-04-25 15:22:44.000000000 +0400
@@ -2114,12 +2114,14 @@
to propagate relevant changes (stop, section table
changed, ...) up to other layers. */
SOLIB_ADD (NULL, 0, ¤t_target, auto_solib_add);
- target_terminal_inferior ();
+
/* Try to reenable shared library breakpoints, additional
code segments in shared libraries might be mapped in now. */
re_enable_breakpoints_in_shlibs ();
+ target_terminal_inferior ();
+
/* If requested, stop when the dynamic linker notifies
gdb of events. This allows the user to get control
and place breakpoints in initializer routines for
--===============1317802100==--
---------------------------------------
Received: (at 306267-close) by bugs.debian.org; 20 Nov 2005 19:41:26 +0000
>From [EMAIL PROTECTED] Sun Nov 20 11:41:26 2005
Return-path: <[EMAIL PROTECTED]>
Received: from katie by spohr.debian.org with local (Exim 4.50)
id 1Eduv4-0002rM-Ke; Sun, 20 Nov 2005 11:32:10 -0800
From: Daniel Jacobowitz <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
X-Katie: $Revision: 1.56 $
Subject: Bug#306267: fixed in gdb 6.3.90.20051119-1
Message-Id: <[EMAIL PROTECTED]>
Sender: Archive Administrator <[EMAIL PROTECTED]>
Date: Sun, 20 Nov 2005 11:32:10 -0800
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level:
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2005_01_02
X-CrossAssassin-Score: 5
Source: gdb
Source-Version: 6.3.90.20051119-1
We believe that the bug you reported is fixed in the latest version of
gdb, which is due to be installed in the Debian FTP archive:
gdb_6.3.90.20051119-1.diff.gz
to pool/main/g/gdb/gdb_6.3.90.20051119-1.diff.gz
gdb_6.3.90.20051119-1.dsc
to pool/main/g/gdb/gdb_6.3.90.20051119-1.dsc
gdb_6.3.90.20051119-1_i386.deb
to pool/main/g/gdb/gdb_6.3.90.20051119-1_i386.deb
gdb_6.3.90.20051119.orig.tar.gz
to pool/main/g/gdb/gdb_6.3.90.20051119.orig.tar.gz
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [EMAIL PROTECTED],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Daniel Jacobowitz <[EMAIL PROTECTED]> (supplier of updated gdb package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [EMAIL PROTECTED])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Sun, 20 Nov 2005 13:40:44 -0500
Source: gdb
Binary: gdb
Architecture: source i386
Version: 6.3.90.20051119-1
Distribution: unstable
Urgency: low
Maintainer: Daniel Jacobowitz <[EMAIL PROTECTED]>
Changed-By: Daniel Jacobowitz <[EMAIL PROTECTED]>
Description:
gdb - The GNU Debugger
Closes: 261330 293637 298088 306267 309538 317317 320391 323217 326358 328580
332184
Changes:
gdb (6.3.90.20051119-1) unstable; urgency=low
.
* New upstream snapshot (6.4 branch prerelease).
- Many Debian patches merged.
- Selected frame and C++ pass-by-reference patches updated.
- Fixes segfault when executing malformed TUI window commands
(Closes: #317317).
- Behaves more gracefully when the executable disappears, et cetera
(Closes: #293637, #323217, #332184).
- Handle vfork from threaded programs using NPTL (Closes: #320391).
* Do not rebuild bfd.info.
* Build depend on a version of debhelper which will put menu fils
in /usr/share.
* Don't build depend on gcj on the Hurd (Closes: #298088).
* Prevent unnecessary SIGTTOU when resolving pending breakpoints
(Closes: #306267).
* Enable the testsuite on amd64.
* Use libreadline5 instead of libreadline4 (Closes: #309538, #326358).
* Install gdb_gcore.sh as gcore (Closes: #328580).
* Add GPC support (Closes: #261330).
Files:
85efb361d8a541dc8b97de99328d36ba 1328 devel standard gdb_6.3.90.20051119-1.dsc
45eb316dbe9707a7d3d9a6876810cfc5 19098755 devel standard
gdb_6.3.90.20051119.orig.tar.gz
22209abda56bd21458667345b87e388e 39594 devel standard
gdb_6.3.90.20051119-1.diff.gz
ac0dd81e033ae31ae474dbb013187594 2755846 devel standard
gdb_6.3.90.20051119-1_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
iD8DBQFDgMr8bgOPXuCjg3cRAlDQAJ9zZpAPVvXIaz2yBeEGoNSMbSwMzACeM9Wh
f2itNxL8eNKs5iLT58y28qE=
=L9L2
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
