[Bug python/31920] blaze types have different behaviour in python interactive and in pretty print

[rmschaich at outlook dot com]

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

Manuel Schaich <rmschaich at outlook dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |NOTABUG
             Status|UNCONFIRMED                 |RESOLVED

--- Comment #2 from Manuel Schaich <rmschaich at outlook dot com> ---
Thank you very much for your feedback! You are right! I made a little
standalone codespaces (https://github.com/worc4021/blaze-gdb-pretty) to be able
to point out line numbers etc. when I realised that when I register the pretty
printer I hadn't been stripping the type definitions! This does fix the issue!
Thank you very much!

One anomaly that remains though, how was it calling "the right code" if it
thought the object was of type "mat". The error during the pretty print is

[...]Python Exception <class 'gdb.error'>: There is no member or method named
m_[...]

should it not just have done no pretty printing at all? After all to all it
knew the object I was printing out was of type "mat" and the pretty printer was
registered for things starting with blaze:: ... Not really an issue since this
solved it. Still a little strange.

Thank you very much for your help!

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