public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "dje at google dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug server/16081] New: excessive copies of library list sent "running to main" Date: Wed, 23 Oct 2013 18:47:00 -0000 [thread overview] Message-ID: <bug-16081-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=16081 Bug ID: 16081 Summary: excessive copies of library list sent "running to main" Product: gdb Version: HEAD Status: NEW Severity: normal Priority: P2 Component: server Assignee: unassigned at sourceware dot org Reporter: dje at google dot com While collecting data for bug 16080 I also see excessive copies of the library list sent while "running to main". The library list is sent 5 times and with 3k libraries that's a lot. Each time is 65 packets to send entire list. [The list is sent in chunks because it's too big to read in one packet. I counted the number of times the list was sent by counting the number of times the last chunk was sent. Also, I'm not including the first time when the list only contains ld.so.] See https://sourceware.org/bugzilla/show_bug.cgi?id=16080 for repro. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2013-10-23 18:47 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-10-23 18:47 dje at google dot com [this message] 2013-10-24 15:29 ` [Bug server/16081] " gbenson at redhat dot com 2013-11-05 19:31 ` gbenson at redhat dot com 2013-11-05 23:33 ` dje at google dot com 2013-11-06 12:39 ` gbenson at redhat dot com
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-16081-4717@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).