Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Nick Roberts <nickrob@snap.net.nz>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sourceware.org,
		Jan Kratochvil <jan.kratochvil@redhat.com>,
		Chet Ramey <chet.ramey@case.edu>
Subject: Re: [patch] Fix testsuite annotate-quit race (PR 544)
Date: Sun, 23 Mar 2008 11:01:00 -0000	[thread overview]
Message-ID: <18406.14411.437345.335844@kahikatea.snap.net.nz> (raw)
In-Reply-To: <20080321214448.GB29593@caradoc.them.org>

 > > I'm running some stress tests with this patch.  So far it hasn't
 > > failed once.
 > 
 > Checked in as so.
 > 
 > -- 
 > Daniel Jacobowitz
 > CodeSourcery
 > 
 > 2008-03-21  Daniel Jacobowitz  <dan@codesourcery.com>
 > 
 > 	PR gdb/544
 > 	Suggested by Jan Kratochvil:
 > 	* top.c (gdb_rl_operate_and_get_next_completion): Call
 > 	rl_redisplay_function.
 > 	(gdb_rl_redisplay): New.
 > 	(init_main): Set rl_redisplay_function.

This change breaks things for Emacs (I have this strange feeling of deja
vu...).

Did your stress tests include running Gdb on a dumb terminal?

I haven't the faintest idea what the problem is and everything seems fine on
an xterm:

nickrob@kahikatea:~$ src-head/build/gdb/gdb -ann=3 myprog
GNU gdb 6.8.50.20080323-cvs
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-pc-linux-gnu"...

^Z^Zpre-prompt
(gdb) 
^Z^Zprompt

but if I do the same from within Emacs, the annotations don't appear.

If you've not got Emacs 22.1, you can see it in an earlier version by doing
M-x shell and "gdb -ann=3" in the *shell* buffer.

-- 
Nick                                           http://www.inet.net.nz/~nickrob


  reply	other threads:[~2008-03-23 11:01 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-18 22:55 Jan Kratochvil
2008-03-18 23:18 ` Daniel Jacobowitz
2008-03-19  8:11   ` Jan Kratochvil
2008-03-19  8:46     ` Nick Roberts
2008-03-19  9:31       ` Jan Kratochvil
2008-03-19  9:56         ` Nick Roberts
2008-03-19 10:13           ` Jan Kratochvil
2008-03-21 20:45     ` Jan Kratochvil
2008-03-21 21:04       ` Daniel Jacobowitz
2008-03-21 21:45         ` Daniel Jacobowitz
2008-03-23 11:01           ` Nick Roberts [this message]
2008-03-23 16:30             ` Daniel Jacobowitz
2008-03-23 16:44               ` Jan Kratochvil
2008-03-23 17:30                 ` Daniel Jacobowitz
2008-03-24  0:07                   ` Nick Roberts
2008-03-24  2:58                     ` Daniel Jacobowitz
2008-03-24  7:42                       ` Jan Kratochvil
2008-03-24 12:00                         ` Daniel Jacobowitz
2008-03-24 13:03                           ` Jan Kratochvil
2008-03-24 13:27                             ` Daniel Jacobowitz
2008-03-25  1:02                       ` Chet Ramey
2008-03-25  2:53                         ` Daniel Jacobowitz
2008-03-25 15:56                           ` Chet Ramey

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=18406.14411.437345.335844@kahikatea.snap.net.nz \
    --to=nickrob@snap.net.nz \
    --cc=chet.ramey@case.edu \
    --cc=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox