Peter Williams

Actually maybe it's fairer to say that the #defines expect the cur_chr to be offset by XETEX_INT, but that doesn't happen in conv_toks in this case.

Mistaken UTF16 decoding in get_next

MemoryReader fails when not all spws/bands have same numebr of channels

Fix confirmed! Thanks for the prompt reply. (Also it's super lucky that I saw it, since I didn't get any email notification from SourceForge about your reply — just happened to check back here since I needed to update my aoflagger build for an entirely different reason. I am not a big fan of the GitHub monoculture but I would say that its communication tools are much better ...)

Fix confirmed! Thanks for the prompt reply. (Also it's super lucky that I saw it, since I didn't get any email notification from SourceForge about your reply — just happened to check back here since I needed to update my aoflagger build for an entirely different reason. I am not a big fan of the GitHub monoculture but I would say that its communication tools are much better ...(

The crash occurs regardless of whether I specify -direct-read, -indirect-read, or -memory-read. Backtrace (I think this is the crashing thread; thread apply all bt produces a whooole lot of text): #0 0x00007ffff518968a in rfiStrategy::FrequencySelectionAction::Perform(rfiStrategy::ArtifactSet&, ProgressListener&) () from /users/pwilliam/env/bin/../lib/libaoflagger.so.0 #1 0x00007ffff52180ee in rfiStrategy::CombineFlagResults::Perform(rfiStrategy::ArtifactSet&, ProgressListener&) () from /users/pwilliam/env/bin/../lib/libaoflagger.so.0...

Memory management problem in 2.10

Logic typo in the WEB source