News for hackers. Stuff that matters.
Re:Why is there a “V” in SIGSEGV Segmentation Fault? by matja on Thursday June 18, 2020 @10:24AM (#23563369)
Interesting problem - what's the shortest C function that takes a pointer to bytes and returns the length of the x86-64 instruction there? (and how many hours would it take to code it)
Re:Why is there a “V” in SIGSEGV Segmentation Fault? by loeg on Thursday June 18, 2020 @11:17AM (#23563848)
Re:Why is there a “V” in SIGSEGV Segmentation Fault? by mhh__ on Thursday June 18, 2020 @08:47PM (#23569833)
The cheating way is probably to do this https://www.blackhat.com/docs/us-17/thursday/us-17-Domas-Bre... (page ~71) i.e. shift across an instruction boundary.
Re:Why is there a “V” in SIGSEGV Segmentation Fault? by kccqzy on Thursday June 18, 2020 @11:01PM (#23570538)
Put it on a page boundary. Make sure the next page isn't accessible. Analyze the resulting page fault.