News for hackers. Stuff that matters.
Re:Rust on AVR: Safer microcontrollers almost here by staticassertion on Saturday February 11, 2017 @10:17AM (#13622964)
Not really. We can simply expand it to "All code has bugs", and then we're simply at Rice's theorem. In C, the class of bugs that can not be proven to not exist are also quite dangerous - remote code execution, as an exemplar consequence. In rust, you're limited to a program that can crash, or that has other semantic faults.

So it's clearly not wrong, and is actually a totally well established idea well outside of the context of rust or C.

Re:Rust on AVR: Safer microcontrollers almost here by Thrillington on Sunday February 12, 2017 @12:36AM (#13626954)
An 8-bit AVR executes instructions from on board flash memory that requires twiddling hardware lines to erase and rewrite.

Remote code execution isn't a concern.

Re:Rust on AVR: Safer microcontrollers almost here by boznz on Monday February 13, 2017 @06:53PM (#13640016)
AVR ATMega is self programmable ie a bootloader can re-flash it if its configured to allow but you would need some code already resident on the flash to allow, it couldnt be done without this code.
Re:Rust on AVR: Safer microcontrollers almost here by pjmlp on Sunday February 12, 2017 @06:33AM (#13627897)
No, but memory corruption related to pointers misuse or unsigned arithmetic is.
Re:Rust on AVR: Safer microcontrollers almost here by dbaupp on Sunday February 12, 2017 @10:38PM (#13632960)
(I think you mean signed arithmetic here and in your almost-sibling comment.)
Re:Rust on AVR: Safer microcontrollers almost here by pjmlp on Monday February 13, 2017 @01:45AM (#13633552)
Probably, I always mix them up.
Re:Rust on AVR: Safer microcontrollers almost here by milesrout on Sunday February 12, 2017 @01:58AM (#13627179)
You can very easily have all the sorts of memory unsafety you have in C, in Rust.
Re:Rust on AVR: Safer microcontrollers almost here by pjmlp on Sunday February 12, 2017 @06:31AM (#13627893)
Only in sections marked as unsafe.

In C every single line of code that manipulates pointers, does string operations, uses arrays or unsigned arithmetic is a possible cause of memory corruption.