From: "dsmith at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug testsuite/10732] declaration.exp empty-struct always fails, resolve-fail passes erroneously
Date: Mon, 04 Jan 2010 15:24:00 -0000 [thread overview]
Message-ID: <20100104152435.30856.qmail@sourceware.org> (raw)
In-Reply-To: <20091004153141.10732.mjw@redhat.com>
------- Additional Comments From dsmith at redhat dot com 2010-01-04 15:24 -------
I'm thinking it should be removed.
If we want to test that one module can implicitly provide a struct
declaration for a probe in some other module, the safest way might be to
write/compile/install a couple of custom kernel modules. But, that seems like
overkill for a situation that '@cast' is designed to solve.
--
http://sourceware.org/bugzilla/show_bug.cgi?id=10732
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next prev parent reply other threads:[~2010-01-04 15:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-04 15:31 [Bug testsuite/10732] New: " mjw at redhat dot com
2009-10-06 2:38 ` [Bug testsuite/10732] " jistone at redhat dot com
2009-12-28 11:13 ` mjw at redhat dot com
2010-01-04 15:24 ` dsmith at redhat dot com [this message]
2010-01-05 10:47 ` mjw at redhat dot com
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=20100104152435.30856.qmail@sourceware.org \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).