public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug remote/30770] serial.c does not preserve errno correctly Date: Fri, 19 Jan 2024 18:10:41 +0000 [thread overview] Message-ID: <bug-30770-4717-xXmR82OUOB@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-30770-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=30770 --- Comment #12 from Sourceware Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Tom Tromey <tromey@sourceware.org>: https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=74d8fa2df7e7844f9b1b8fac27fe7d0b82100ab0 commit 74d8fa2df7e7844f9b1b8fac27fe7d0b82100ab0 Author: СеÑгей ЧеÑнов <klen_s@mail.ru> Date: Fri Jan 19 11:01:18 2024 -0700 Fix remote serial read After closing "Bug 30770 - serial.c does not preserve errno correctly" https://sourceware.org/bugzilla/show_bug.cgi?id=30770 remote debugging became impossible due to an attempt to recv() by a call intended for the socket, and not for the character device file. The documentation implicitly states that it is possible to use the read() call to work with a socket. But this does not mean in the general case that it is permissible to use recv in the case of a non-socket. condition: os: Distributor ID: Ubuntu Description: Ubuntu 23.10 Release: 23.10 Codename: mantic libc: ldd (Ubuntu GLIBC 2.38-1ubuntu6) 2.38 kernel: Linux klen-dev-um790pro 6.5.0-14-generic #14-Ubuntu SMP PREEMPT_DYNAMIC Tue Nov 14 14:59:49 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux gdb: build from trank at 15.0.50.20231226-git GDB output: $ arm-kgp-eabi-gdb GNU gdb (Klen's_GNU_package_(KGP)_for_target::arm-kgp-eabi<rmprofile/lto>_host::x86_64-kgp-linux-gnu_znver4-avx512<<ílex>>) 15.0.50.20231226-git .... (gdb) tar ext /dev/ttyACM1 Remote debugging using /dev/ttyACM1 Remote communication error. Target disconnected: error while reading: Socket operation on non-socket. (gdb) after fix gdb work fine $ arm-kgp-eabi-gdb -q (gdb) tar ext /dev/ttyACM0 Remote debugging using /dev/ttyACM0 (gdb) mon swd Target voltage: 0.0V Available Targets: No. Att Driver STM32F40x M4 (gdb) att 1 Attaching to Remote target warning: No executable has been specified and target does not support determining executable automatically. Try using the "file" command. 0x08020c80 in ?? () (gdb) Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=30770 -- You are receiving this mail because: You are on the CC list for the bug.
prev parent reply other threads:[~2024-01-19 18:10 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-08-16 14:11 [Bug remote/30770] New: " tromey at sourceware dot org 2023-08-29 12:53 ` [Bug remote/30770] " tromey at sourceware dot org 2023-08-29 13:48 ` tromey at sourceware dot org 2023-08-31 13:20 ` tromey at sourceware dot org 2023-09-12 16:27 ` tromey at sourceware dot org 2023-09-12 16:28 ` tromey at sourceware dot org 2023-11-27 20:14 ` cvs-commit at gcc dot gnu.org 2023-11-27 20:14 ` cvs-commit at gcc dot gnu.org 2023-11-27 20:14 ` cvs-commit at gcc dot gnu.org 2023-11-27 20:14 ` cvs-commit at gcc dot gnu.org 2023-11-27 20:14 ` cvs-commit at gcc dot gnu.org 2023-11-27 20:14 ` cvs-commit at gcc dot gnu.org 2023-11-27 23:29 ` tromey at sourceware dot org 2024-01-19 18:10 ` cvs-commit at gcc dot gnu.org [this message]
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=bug-30770-4717-xXmR82OUOB@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.org \ /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: linkBe 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).