No, I don't know of a way to do that, and I'd be surprised if there was an easy one (ie, one that I have remotely the low-level knowledge to implement). But someone who knows more about the system level might have better ideas. <div> </div><div>Sam</div> <div class="gmail_quote">On Thu Dec 04 2014 at 12:01:30 PM Robby Findler <<a href="mailto:robby@eecs.northwestern.edu">robby@eecs.northwestern.edu</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Do you know how to get the racket-level stack at the point strace reports a call to open() or write()? (I do see this bug occasionally but not reproducibly so setting up something on my machine with more debugging output seems likely to be productive.) Robby On Thu, Dec 4, 2014 at 10:34 AM, Sam Tobin-Hochstadt <<a href="mailto:samth@cs.indiana.edu" target="_blank">samth@cs.indiana.edu</a>> wrote: > > > On Thu Dec 04 2014 at 9:36:08 AM Robby Findler <<a href="mailto:robby@eecs.northwestern.edu" target="_blank">robby@eecs.northwestern.edu</a>> > wrote: >> >> On Wed, Dec 3, 2014 at 10:30 PM, Prabhakar Ragde <<a href="mailto:plragde@uwaterloo.ca" target="_blank">plragde@uwaterloo.ca</a>> >> wrote: >> > I'm currently using Racket 6.1. For some time now, when editing Scribble >> > files in DrRacket, I've been getting "file has changed on disk" messages >> > when trying to save or render - not consistently, just every so often. >> > These >> > are files I am not editing in anything other than DrRacket. I click >> > "ignore" >> > and everything works fine, but it is annoying. >> >> This is definitely a bug somewhere and I've had not a lot of luck >> tracking it down. >> >> >> I guess that what's happening is something is actually changing the >> file on the disk (perhaps DrRacket itself) and it shouldn't. >> >> So if you can figure out what feature of DrRacket is making this >> happen or verify that the file is actually not changing on the disk, >> either of those would be helpful. > > > Here's a thought on tracking it down: > > * Run DrRacket under strace, looking at the calls to `open()` and `write()`. > > * Add to relevant places in DrRacket something like this: > (access string F_OK) > > where `access` is an FFI call to the C library access function, and F_OK is > the appropriate constant. Then those messages will appear in the strace > output, so you can see what DrRacket is doing right around the time it opens > or writes to the relevant file. > > I got this trick from here: > <a href="https://people.gnome.org/~federico/news-2006-03.html#09" target="_blank">https://people.gnome.org/~federico/news-2006-03.html#09</a> where it's used to > plot timelines (also cool) but it might be useful for debugging in this > case. > > Sam </blockquote></div>