This is the mail archive of the gdb-prs@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug python/18438] New: PyExc_MemoryError != gdbpy_gdb_memory_error


https://sourceware.org/bugzilla/show_bug.cgi?id=18438

            Bug ID: 18438
           Summary: PyExc_MemoryError != gdbpy_gdb_memory_error
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: python
          Assignee: unassigned at sourceware dot org
          Reporter: dje at google dot com
  Target Milestone: ---

A user is getting the following in a backtrace:

...
#7  0x000000000040bac0 in operator<< <char, std::char_traits<char>,
std::allocator<char> > (__os=warning: RTTI symbol not found for class
'std::ostream'
..., Traceback (most recent call last):
  File "/foo/printers.py", line 38, in to_string
    return ptr.lazy_string (length = length)
MemoryError: Cannot create a lazy string with address 0x0, and a non-zero
length.
__str=
) at bar/string:927
#8  0x000000000040ba55 in main () at baz.cc:10

The RTTI error is a separate bug (IIRC PR 18141, PR 18417 - there are multiple
bugs here, I could be forgetting one).

This bug is the python backtrace being printed when there's a memory error.
That's not supposed to happen.

The bug arises because PyExc_MemoryError is being used instead of
gdbpy_gdb_memory_error. Patch to follow.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]