Re: volatile pointers clobbered by 'longjmp'

Article View: gnu.gcc.help

Article #53290

#53290

From: djanssen
Date: Mon, 24 Feb 1992 13:44

15 lines
890 bytes

Hi,

I got a reply from Robert Earl concerning the volatile pointers
which were being 'clobbered' by 'longjmp'. He said:

    void	volatile	*buf_ptr = NULL_PTR;

    means: buf_ptr points to a volatile object, while

    void	*volatile	buf_ptr	= NULL_PTR;

    means: buf_ptr is a volatile pointer.

I tried it and it solved my problem, (-:} Many thanks,
    							Ton Janssen

Technical Details

Message-ID: <130844.29a8f6aa@mswe.dnet.ms.philips.nl>

Path: arc1-ca.pugleaf.net!sparky!uunet!mcsun!sun4nl!phigate!mswe!djanssen

Show Full Headers

Complete Article Headers

X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 11318c,9598e995c4cae923,start
X-Google-Attributes: gid11318c,public
X-Google-ArrivalTime: 1992-02-25 21:54:24 PST
Path: arc1-ca.pugleaf.net!sparky!uunet!mcsun!sun4nl!phigate!mswe!djanssen
From: djanssen@mswe.dnet.ms.philips.nl
Newsgroups: gnu.gcc.help
Subject: Re: volatile pointers clobbered by 'longjmp'
Message-ID: <130844.29a8f6aa@mswe.dnet.ms.philips.nl>
Date: 24 Feb 92 13:44:10 GMT
Organization: Philips Medical Systems Nederland
Lines: 15