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

On Sun, 23 Mar 2008 17:30:27 +0100, Daniel Jacobowitz wrote:
...
> I tried running gdb under nohup and it worked fine.  I tried it in
> Emacs too, and that worked fine:

Confirmed the patch broke emacs-22.1-8.fc8.x86_64 (M-x shell ...).  readline
checks for custom RL_REDISPLAY_FUNCTION and behaves differently in such case.
Sorry for suggesting RL_REDISPLAY_FUNCTION - I did not verify it more.
Now just to find out how to supply GDB_RL_REDISPLAY simulating the original
behavior.

latest GDB:
rt_sigaction(SIGWINCH, {0x5f9025, [], SA_RESTORER|SA_RESTART, 0x3b98630f30}, {0x4ab21a, [], SA_RESTORER, 0x3b98630f30}, 8) = 0
rt_sigprocmask(SIG_BLOCK, [INT], [CHLD], 8) = 0
rt_sigprocmask(SIG_SETMASK, [CHLD], NULL, 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [CHLD], 8) = 0
poll([{fd=3, events=POLLIN}, {fd=0, events=POLLIN, revents=POLLIN}], 2, -1) = 1
rt_sigprocmask(SIG_BLOCK, NULL, [CHLD], 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [CHLD], 8) = 0
read(0, "q", 1)                         = 1

reverted patch:
rt_sigaction(SIGWINCH, {0x5f8fb5, [], SA_RESTORER|SA_RESTART, 0x3b98630f30}, {0x4ab1aa, [], SA_RESTORER, 0x3b98630f30}, 8) = 0
write(1, "\n\32\32pre-prompt\n(gdb) \n\32\32prompt\n", 30) = 30
rt_sigprocmask(SIG_BLOCK, NULL, [CHLD], 8) = 0
poll([{fd=3, events=POLLIN}, {fd=0, events=POLLIN, revents=POLLIN}], 2, -1) = 1
rt_sigprocmask(SIG_BLOCK, NULL, [CHLD], 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [CHLD], 8) = 0
read(0, "q", 1)                         = 1


> Does reverting the patch fix the problem?

Yes.


Regards,
Jan


  reply	other threads:[~2008-03-23 16:44 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
2008-03-23 16:30             ` Daniel Jacobowitz
2008-03-23 16:44               ` Jan Kratochvil [this message]
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=20080323164331.GA1195@host0.dyn.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=chet.ramey@case.edu \
    --cc=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=nickrob@snap.net.nz \
    /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