)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":1000021,"name":"Antonio Borneo","email":"borneo.antonio@gmail.com","username":"borneoa"},"change_message_id":"dad2f9efed77735bfbf6b9cc9f21000360b58398","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"7a6f0a9e_d83cdce0","updated":"2024-06-01 16:53:39.000000000","message":"Yes, it looks correct!\nBut this only works in multi targets case where user runs command ``gdb_port pipe``, valid for all targets.\nIf user runs ``$targetname configure -gdb-port pipe`` on more than one target, we get in the same issue. We would need something like a static flag to keep info on the first ``pipe`` targets and use ``disabled`` if a following one try to use ``pipe`` too, either from ``configure`` or from ``gdb_port pipe``.\nOr this check should be moved in ``server.c:add_service()``, because user can also ask a telnet server on pipe!\nMaybe these odd cases in a future improvement ...","commit_id":"d968fb720236925f3f0e7cb1900b9ec10ea63aae"},{"author":{"_account_id":1000160,"name":"Paul Fertser","email":"fercerpav@gmail.com","username":"pfertser"},"change_message_id":"b639bba4baa5a67ccb2f8f434a999867dc47a844","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"259e51b3_095503ad","in_reply_to":"7a6f0a9e_d83cdce0","updated":"2024-06-01 17:09:41.000000000","message":"\u003e If user runs ``$targetname configure -gdb-port pipe`` on more than one target, we get in the same issue.\n\nRight, but is it likely to happen in real life? Do people configure gdb-port to pipe ever that way even for a single target?\n\n\u003e Maybe these odd cases in a future improvement ...\n\nI\u0027d say the current patch fixes a bug while the improvements are about adding some guardrails which are useful of course but not essential.","commit_id":"d968fb720236925f3f0e7cb1900b9ec10ea63aae"}]}