public inbox for gdb-testers@sourceware.org help / color / mirror / Atom feed
From: sergiodj+buildbot@sergiodj.net To: gdb-testers@sourceware.org Subject: [binutils-gdb] Fix ptype/o comment formatting Date: Wed, 08 May 2019 17:35:00 -0000 [thread overview] Message-ID: <844333e24966817fe4d622494a75c8ae0acdb91f@gdb-build> (raw) *** TEST RESULTS FOR COMMIT 844333e24966817fe4d622494a75c8ae0acdb91f *** Author: Tom Tromey <tromey@adacore.com> Branch: master Commit: 844333e24966817fe4d622494a75c8ae0acdb91f Fix ptype/o comment formatting I noticed that ptype/o will print: /* 3: 3 | 1 */ signed char a4 : 2; /* XXX 3-bit hole */ That is, "*/" at the end of the "hole" message does not line up with the other comment ends. I thought it would be a bit nicer if this did line up, so I fixed it. Then, to my surprise, I found that I could not make ptype-offsets.exp fail. I still am not sure why it doesn't fail, but changing the tests to use string_to_regexp and changing the quoting helped. This in turn showed that some of the existing test cases were wrong, so I've also updated them here. gdb/ChangeLog 2019-05-08 Tom Tromey <tromey@adacore.com> * typeprint.c (print_offset_data::maybe_print_hole): Add extra padding at end of comment. gdb/testsuite/ChangeLog 2019-05-08 Tom Tromey <tromey@adacore.com> * gdb.base/ptype-offsets.exp: Use string_to_regexp. Fix test cases. * gdb.base/ptype-offsets.cc (struct abc) <my_int_type>: Now "short".
next reply other threads:[~2019-05-08 17:35 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-05-08 17:35 sergiodj+buildbot [this message] 2019-05-08 17:50 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, branch master sergiodj+buildbot 2019-05-08 17:55 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot 2019-05-08 18:05 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot 2019-05-08 18:08 ` Failures on Fedora-i686, " sergiodj+buildbot 2019-05-08 18:11 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot 2019-05-08 18:48 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot 2019-05-08 20:19 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot
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=844333e24966817fe4d622494a75c8ae0acdb91f@gdb-build \ --to=sergiodj+buildbot@sergiodj.net \ --cc=gdb-testers@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: 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).