Path: utzoo!utgpu!watmath!iuvax!cica!tut.cis.ohio-state.edu!AI.MIT.EDU!kingdon From: kingdon@AI.MIT.EDU (Jim Kingdon) Newsgroups: gnu.gdb.bug Subject: volatle is broken (at least for remote) Message-ID: <8909272158.AA06450@hobbes.ai.mit.edu> Date: 27 Sep 89 21:58:24 GMT References: <8909271659.AA23091@tfd.uucp> Distribution: gnu Organization: GNUs Not Usenet Lines: 13 I have disabled the remote caching stuff completely to fix this problem. The other person who noticed this bug didn't notice much of a performance hit when he did this, so I don't see any reason to worry about the lost caching. Thanks for your bug report. volatile char *led = 0x180001; This is unreleated to the GDB problem, since the remote debugging cache didn't check for "volatile", but I'm not sure this is the right declaration. Doesn't this say "volatile pointer to character" rather than "pointer to volatile character"? Perhaps you mean "char volatile * led" (but don't quote me on that; I've never fully figured out type qualifiers in C).