public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gustaf.waldemarson at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/107965] libstdc++ Python Pretty-Printers: Many Exceptions From Uninitialized Structures Date: Tue, 17 Jan 2023 19:37:01 +0000 [thread overview] Message-ID: <bug-107965-4-FdFPLgkGXT@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107965-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107965 --- Comment #7 from Gustaf Waldemarson <gustaf.waldemarson at gmail dot com> --- Very interesting to see so many people chime in on this. Since I arguably agree that this looks like a GDB bug than an error in the printers. To that end, I went ahead and registered this [ticket](https://sourceware.org/bugzilla/show_bug.cgi?id=30018) here. Please feel free to add some more details if you have time, as some of the details presented here is admittedly a bit beyond my skills. All that said, I still think that the pretty printers should be a bit more defensive to errors and conservative with what it outputs. E.g., presenting an error message once, due to something like this is fine in my opinion, but displaying hundreds of lines with the same error just because some function uses a hash-map is clearly excessive. To that end, perhaps it would make sense to defend the `to_string` calls (and possibly others) with something like this: seen_errors = {} # ... try: to_string(...) except Exception as ex: if ex not in seen_errors: seen_errors.add(ex) raise ex Admittedly, I don't know all the details here, so perhaps this isn't feasible?
next prev parent reply other threads:[~2023-01-17 19:37 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-12-04 19:46 [Bug libstdc++/107965] New: " gustaf.waldemarson at gmail dot com 2022-12-04 20:04 ` [Bug libstdc++/107965] " pinskia at gcc dot gnu.org 2022-12-05 8:24 ` redi at gcc dot gnu.org 2022-12-05 8:45 ` rguenth at gcc dot gnu.org 2022-12-05 8:48 ` rguenth at gcc dot gnu.org 2022-12-05 9:42 ` [Bug debug/107965] " redi at gcc dot gnu.org 2022-12-05 10:37 ` redi at gcc dot gnu.org 2023-01-17 19:37 ` gustaf.waldemarson at gmail dot com [this message] 2023-01-17 20:25 ` jason 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-107965-4-FdFPLgkGXT@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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).