How I fixed libuv

#1

Post by adamnemecek » Sat, Jan 23, 2016, 6:01 PM UTC

How I fixed libuv
davidvgalbraith.com

Re: How I fixed libuv

#2

Post by saghul » Sun, Jan 24, 2016, 11:19 AM UTC

This is great and thorough explanation, thanks Dave for following all the issue deep down the rabbit hole :-)

Disclaimer: I'm one of the libuv maintainers.

Re: How I fixed libuv

#3

Post by legulere » Sun, Jan 24, 2016, 11:37 AM UTC

It's probably overly pedantic of me, but:

> Segmentation faults happen in C when a program makes an invalid memory access.

Segmentation faults CAN happen, but don't need to. Just as likely some padding space (no effect at all), program data (some of your data will contain garbage) or code pointers (worst case! this means arbitrary code execution) can be overwritten.

Re: How I fixed libuv

#4

Post by chris_wot » Sun, Jan 24, 2016, 12:07 PM UTC

legulere wrote: post #3

It's probably overly pedantic of me, but: > Segmentation faults happen in C when a program makes an invalid memory access. Segmentation faults CAN happen, but don't need to. Just as likely some padding space (no effect at all), program data (some of your data will contain garbage) or code pointers (worst case! this means arbitrary code execution) can be overwritten.

Dunno why you are being downvoted, that sounds correct to me!

Re: How I fixed libuv

#5

Post by davidvgalbraith » Tue, Feb 02, 2016, 7:40 PM UTC

legulere wrote: post #3

It's probably overly pedantic of me, but: > Segmentation faults happen in C when a program makes an invalid memory access. Segmentation faults CAN happen, but don't need to. Just as likely some padding space (no effect at all), program data (some of your data will contain garbage) or code pointers (worst case! this means arbitrary code execution) can be overwritten.

Thanks! Updated the post with "Segmentation faults can happen in C..."