public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "dinc.tarkan at gmail dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/27627] GDB cannot get long threadinfo data over UDP Date: Tue, 06 Apr 2021 06:13:24 +0000 [thread overview] Message-ID: <bug-27627-4717-Z9K5bAJKMG@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-27627-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=27627 --- Comment #5 from Tarkan <dinc.tarkan at gmail dot com> --- UDP works over a decade for us. Tried on emulator (qemu) so no physical connection, and no reliability problem and still same problem. Also TCP is much slower on windows. Tried to TCP_NODELAY option, but that cause another problems. It's better for us if we can use UDP. -- You are receiving this mail because: You are on the CC list for the bug.
prev parent reply other threads:[~2021-04-06 6:13 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-23 8:05 [Bug gdb/27627] New: " dinc.tarkan at gmail dot com 2021-03-29 16:02 ` [Bug gdb/27627] " tromey at sourceware dot org 2021-04-05 5:36 ` dinc.tarkan at gmail dot com 2021-04-05 5:43 ` dinc.tarkan at gmail dot com 2021-04-05 14:42 ` simark at simark dot ca 2021-04-06 6:13 ` dinc.tarkan at gmail dot com [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-27627-4717-Z9K5bAJKMG@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).