public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "dov.grobgeld at gmail dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug mi/14081] New: -file-list-exec-source-files should weed out duplicates Date: Wed, 09 May 2012 05:56:00 -0000 [thread overview] Message-ID: <bug-14081-4717@http.sourceware.org/bugzilla/> (raw) http://sourceware.org/bugzilla/show_bug.cgi?id=14081 Bug #: 14081 Summary: -file-list-exec-source-files should weed out duplicates Product: gdb Version: unknown Status: NEW Severity: normal Priority: P2 Component: mi AssignedTo: unassigned@sourceware.org ReportedBy: dov.grobgeld@gmail.com Classification: Unclassified -file-list-exec-source-files currently does not run "uniq" on its output. The result is that the same file names may appear multiple times. In an example run on an executable from my work place, -file-list-exec-source-files generated a text string 3.5MB in size. After postprocessing this file to remove duplicates, the size was reduced to 220k. I propose that mi_cmd_file_list_exec_source_files() be amended to keep a hash table of filenames already output and skips outputting the same filename twice. -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next reply other threads:[~2012-05-09 5:56 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-05-09 5:56 dov.grobgeld at gmail dot com [this message] 2012-05-10 20:55 ` [Bug mi/14081] " dov.grobgeld at gmail dot com 2012-05-11 8:29 ` dov.grobgeld at gmail dot com 2022-02-24 15:14 ` tromey at sourceware dot org
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-14081-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).