Can SIGSEGV caused during a memory read(not write) be ignored?

Can I ignore SIGSEGV caused because of an invalid read(not write)? I am to catching it using a __try {} / __catch{} block since I am writing it in Windows. I am successfully able to catch it and ignore it. My question mainly is since I am only trying to read the memory and not trying to write anything to it, would the read cause corruption? Or is it safe?