The Problem with Friendly C

Re:The Problem with Friendly C by ars on Wednesday December 23, 2015 @10:13PM (#10786898)

Maybe it's a hardware trap and not a regular null reference segmentation fault?

[ Parent | on HN ]

Re:The Problem with Friendly C by pcwalton on Wednesday December 23, 2015 @11:08PM (#10787070)

Well, shl doesn't trap on x86 for out of range values; it just masks the second operand by 0x1f [1]. But it could be some other kind of trap.

Complete guess in the dark: tcc misencoded an instruction causing an illegal instruction trap, maybe in some sort of misguided attempt to optimize the shift to a lea.

[1]: http://x86.renejeschke.de/html/file_module_x86_id_285.html

[ Parent | on HN ]

Re:The Problem with Friendly C by Filligree on Thursday December 24, 2015 @07:23AM (#10787939)

Wouldn't that normally produce SIGILL, not SIGSEGV?

[ Parent | on HN ]