From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-prs-return-7967-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Received: (qmail 26608 invoked by alias); 25 Feb 2010 13:42:04 -0000
Received: (qmail 26579 invoked by uid 48); 25 Feb 2010 13:42:03 -0000
Date: Thu, 25 Feb 2010 13:42:00 -0000
From: "mjw at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Message-ID: <20100225134201.11324.mjw@redhat.com>
Reply-To: sourceware-bugzilla@sourceware.org
Subject: [Bug python/11324] New: python pretty-printers uglify backtraces
X-Bugzilla-Reason: CC
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
X-SW-Source: 2010-q1/txt/msg00338.txt.bz2

This a slightly lame bug report since it is just going on a backtrace provided
by a user and I don't actually have the binary myself:
https://bugzilla.redhat.com/attachment.cgi?id=396257

See the backtrace of thread 1 (starting from frame 11 and later):

#11 0x000000375102a6ca in g_hash_table_lookup_node (hash_table=
    Traceback (most recent call last):
  File "/usr/share/glib-2.0/gdb/glib.py", line 155, in pretty_printer_lookup
    return GHashPrinter(val)
  File "/usr/share/glib-2.0/gdb/glib.py", line 122, in __init__
    if self.val != 0 and string_hash != None and self.val["hash_func"] ==
string_hash:
RuntimeError: Cannot access memory at address 0xaaaaaaaaaaaaaaca
0xaaaaaaaaaaaaaaaa, key=0x3755031684) at ghash.c:195
        node = <value optimized out>
        node_index = <value optimized out>
        hash_value = <value optimized out>
        step = 0

Instead of having the the python backtrace in the middle of the values printed I
would expect a fallback to the "raw gdb" value print for hash_table, probably
just hash_table=0xaaaaaaaaaaaaaaca. Which is likely what it is, it is a bogus
address. No need to tell me that with a python backtrace. Or if you do, please
report just something simple like: hash_table="<error:couldn't pythonfy>"

Having the full python backtrace might be interesting for a pretty-printer
plugin writer, but it should be an option off by default.

-- 
           Summary: python pretty-printers uglify backtraces
           Product: gdb
           Version: archer
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: python
        AssignedTo: unassigned at sourceware dot org
        ReportedBy: mjw at redhat dot com
                CC: gdb-prs at sourceware dot org


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

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.