public inbox for
help / color / mirror / Atom feed
From: "gdb-ml at jaeckel dot eu" <>
Subject: [Bug server/30815] New: gdbserver prints debug info unconditionally to stderr
Date: Thu, 31 Aug 2023 16:22:58 +0000	[thread overview]
Message-ID: <> (raw)

            Bug ID: 30815
           Summary: gdbserver prints debug info unconditionally to stderr
           Product: gdb
           Version: HEAD
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: server
          Assignee: unassigned at sourceware dot org
          Reporter: gdb-ml at jaeckel dot eu
  Target Milestone: ---

Created attachment 15097
A WIP patch to approach the issue.

When debugging an ncurses application that is using other background
processes/threads (like e.g. `profanity`,
`gdbserver` prints `Detaching from process XYZ` directly to stderr after
`profanity` started one of those processes.

This leads to the ncurses window being modified and those debug statements
being printed somewhere on the screen.

Reproducing is possible with e.g. profanity.

1. start profanity in gdbserver

$ gdbserver localhost:1234 profanity

2. connect to said gdbserver instance in another terminal

$ gdb -ex "target remote localhost:1234" -ex continue

3. connect with profanity to an xmpp server

/connect <jid>

Now you will see multiple `Detaching from process XYZ` messages throughout the

I've been able to reproduce some artifacts with `irssi` as well, but it's not
that obvious as with `profanity`.

The patchfile that I've attached solves my initial problem, those messages
aren't printed in the debugged window anymore. Still the patch is not complete
as described in the commit message and I didn't want to invest more time before
I've got the OK that this could be an acceptable solution.

You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2023-08-31 16:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-31 16:22 gdb-ml at jaeckel dot eu [this message]
2023-09-01 12:43 ` [Bug server/30815] " tromey at sourceware dot org

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:

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

  git send-email \ \ \ \

* 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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).