From: Daniel Jacobowitz <drow@mvista.com>
To: gdb-patches@sources.redhat.com
Subject: Re: gdb.c++ testsuite 1: member data
Date: Tue, 14 May 2002 14:34:00 -0000 [thread overview]
Message-ID: <20020514213426.GA13265@nevyn.them.org> (raw)
In-Reply-To: <20020514121358.773176f1.bkoz@redhat.com>
On Tue, May 14, 2002 at 12:13:58PM -0700, Benjamin Kosnik wrote:
> These four files test for data member display in gdb. The first,
> member_data.cc, tests (bool, int, long, enum) data members and then
> tests various combinations of templates, non-POD object, etc. The data
> members tested are not random, and are synthesized to represent common
> constructs in the C++ standard library.
>
> The second does the same, but the data members are static.
>
> As it stands, member_data.cc passes on linux when compiled shared, fails
> when static. The second file, members_data_static.cc, fails always. (And
> has for years, three at least.)
>
> Please let me know what you think, and feel free to check them in. I'd
> really like it if one day these files both passed, for static and shared
> linkage.
>
> Files as attached. I don't have write access to the 'src' module. (And
> it's not especially imperative that I have it.)
>
> tested x86/linux
>
> 2002-05-14 Benjamin Kosnik <bkoz@redhat.com>
>
> * gdb.c++/member_data.cc: New file.
> * gdb.c++/member_data.exp: New file.
> * gdb.c++/member_data_static.cc: New file.
> * gdb.c++/member_data_static.exp: New file.
Ben, thanks a lot for submitting these! We can always use more C++
tests, and I'm at work on the ones we have too much already to add
more. I don't suppose the "1" in the subject means you've got more
coming?
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-05-14 21:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-14 12:14 Benjamin Kosnik
2002-05-14 14:34 ` Daniel Jacobowitz [this message]
2002-05-14 18:56 ` Andrew Cagney
2002-05-14 12:29 Michael Elizabeth Chastain
2002-05-14 14:27 ` Jim Blandy
2002-05-14 17:14 Michael Elizabeth Chastain
2002-05-15 1:44 ` Benjamin Kosnik
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=20020514213426.GA13265@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
/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: link
Be 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