public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
* [Bug server/30815] New: gdbserver prints debug info unconditionally to stderr
@ 2023-08-31 16:22 gdb-ml at jaeckel dot eu
  2023-09-01 12:43 ` [Bug server/30815] " tromey at sourceware dot org
  0 siblings, 1 reply; 2+ messages in thread
From: gdb-ml at jaeckel dot eu @ 2023-08-31 16:22 UTC (permalink / raw)
  To: gdb-prs

https://sourceware.org/bugzilla/show_bug.cgi?id=30815

            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
  --> https://sourceware.org/bugzilla/attachment.cgi?id=15097&action=edit
A WIP patch to approach the issue.

When debugging an ncurses application that is using other background
processes/threads (like e.g. `profanity` https://profanity-im.github.io/),
`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
window.

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.

^ permalink raw reply	[flat|nested] 2+ messages in thread

* [Bug server/30815] gdbserver prints debug info unconditionally to stderr
  2023-08-31 16:22 [Bug server/30815] New: gdbserver prints debug info unconditionally to stderr gdb-ml at jaeckel dot eu
@ 2023-09-01 12:43 ` tromey at sourceware dot org
  0 siblings, 0 replies; 2+ messages in thread
From: tromey at sourceware dot org @ 2023-09-01 12:43 UTC (permalink / raw)
  To: gdb-prs

https://sourceware.org/bugzilla/show_bug.cgi?id=30815

Tom Tromey <tromey at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tromey at sourceware dot org

--- Comment #1 from Tom Tromey <tromey at sourceware dot org> ---
Another option might be to send this back to gdb in "O" packets.
However, this won't work with non-stop.

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

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2023-09-01 12:43 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-08-31 16:22 [Bug server/30815] New: gdbserver prints debug info unconditionally to stderr gdb-ml at jaeckel dot eu
2023-09-01 12:43 ` [Bug server/30815] " tromey at sourceware dot org

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).