public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug symtab/15028] regressions with dwz -m
Date: Mon, 04 Feb 2013 21:12:00 -0000	[thread overview]
Message-ID: <bug-15028-4717-MmRXDsIQiA@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-15028-4717@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=15028

--- Comment #6 from Tom Tromey <tromey at redhat dot com> 2013-02-04 21:12:28 UTC ---
With my various patches in place I see:

gdb.base/dbx.exp: whereis my_list: PASS => FAIL
gdb.cp/namespace.exp: info func xyzq: PASS => FAIL

Both of these are caused by the strange way in which we
invoke dwz -- passing in two identical copies of the same
program.  This means that some objects are duplicated
(once in the .dwz file and another time in the main file,
but usually there with a source location).

It is unclear to me if this kind of thing can ever happen
with a real use of dwz.

-- 
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.


  parent reply	other threads:[~2013-02-04 21:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-17 19:34 [Bug symtab/15028] New: " tromey at redhat dot com
2013-01-17 19:35 ` [Bug symtab/15028] " tromey at redhat dot com
2013-01-28 16:54 ` tromey at redhat dot com
2013-01-28 19:40 ` tromey at redhat dot com
2013-01-29 18:37 ` tromey at redhat dot com
2013-01-30 20:21 ` tromey at redhat dot com
2013-02-04 17:24 ` tromey at redhat dot com
2013-02-04 21:12 ` tromey at redhat dot com [this message]
2013-08-07 19:28 ` tromey at redhat dot com
2013-08-07 20:10 ` cvs-commit at gcc dot gnu.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-15028-4717-MmRXDsIQiA@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: link
Be 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).