From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: cagney@gnu.org, gdb-patches@sources.redhat.com
Subject: Re: [rfa/testsuite] Extend signull to work with discriptors
Date: Wed, 16 Jun 2004 05:02:00 -0000 [thread overview]
Message-ID: <20040616050213.94BCC4B104@berman.michael-chastain.com> (raw)
Needs more work:
- copyright year 2004 in signull.c
- did you test it on ia64 and/or ppc?
can't quite tell from your wording
- this code has ISO problems.
% cat ptr.c
typedef long data_t;
typedef long code_t (void);
volatile data_t zero[10];
volatile code_t *desc = (void *) zero;
% gcc-340 -Wall -S -pedantic -std=iso9899:1990 ptr.c
ptr.c:4: warning: ISO C forbids qualified function types
ptr.c:4: warning: ISO C forbids initialization between function pointer and `void *'
What about:
code_t * volatile desc = 0;
But that's semantically different from what you wrote. Hmmm. I don't
think it's possible in ISO C to initialize a pointer-to-code with the
address of a data object. Any ideas?
Michael C
===
2004-06-15 Andrew Cagney <cagney@gnu.org>
* gdb.base/signull.c (bowler): Replace data_pointer with data_read
and data_write cases. Add code_descriptor case.
(zero, desc): New array and pointer.
(data, code): Change to simple pointers.
* gdb.base/signull.exp: Fix probe pattern matching a function
descriptor SIGSEGV. Replace data_pointer with data_read and
data_write tests.
next reply other threads:[~2004-06-16 5:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-16 5:02 Michael Elizabeth Chastain [this message]
2004-06-16 14:54 ` Andrew Cagney
-- strict thread matches above, loose matches on Subject: below --
2004-06-16 15:39 Michael Elizabeth Chastain
2004-06-16 16:43 ` Andrew Cagney
2004-06-16 2:00 Andrew Cagney
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=20040616050213.94BCC4B104@berman.michael-chastain.com \
--to=mec.gnu@mindspring.com \
--cc=cagney@gnu.org \
--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