Optimizer incorrectly removing part of the code?

[dpc]

My code behaves differently in debug and release mode. In release mode pressing "y" to confirm exiting the game is going to be incorrectly ignored. From my investigation, it seems some part of the match expression is getting completely removed.

The affected code:

https://github.com/dpc/rhex/blob/issue/src/ui/curses.rs#L1119

Uncommenting the info! on line 1119 makes the game generate correct code even in release mode.

[futex:lab/rust]% rustc --version
rustc 1.2.0-nightly (99c2f77 2015-05-29) (built 2015-05-29)

[eddyb]

Sounds like typical undefined behaviour (coming from an unsafe block, hopefully).
Could you reduce the application (by commenting out unrelated chunks of code) while still retaining the bug?

[dpc]

I have a one unsafe in my whole project that is quite distant from affected code, and there's really not much code interaction with dependencies in that code, except getting a character number from ncurses.

I can try to reduce it, sure.

[eddyb]

@dpc I'd expect the issue to be in one your dependencies that uses unsafe code, rather than in your own project.

[arielb1]

@dpc

could you run your code in debug mode under valgrind? that could possibly give an hint.

[dpc]

@arielb1:

[futex:rhex/rhex] (master!)% valgrind ./target/debug/rhex
==11605== Memcheck, a memory error detector
==11605== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==11605== Using Valgrind-3.10.1 and LibVEX; rerun with -h for copyright info
==11605== Command: ./target/debug/rhex
==11605== 
==11605== 
==11605== HEAP SUMMARY:
==11605==     in use at exit: 282,430 bytes in 260 blocks
==11605==   total heap usage: 1,289 allocs, 1,029 frees, 529,137 bytes allocated
==11605== 
==11605== LEAK SUMMARY:
==11605==    definitely lost: 0 bytes in 0 blocks
==11605==    indirectly lost: 0 bytes in 0 blocks
==11605==      possibly lost: 1,728 bytes in 3 blocks
==11605==    still reachable: 280,702 bytes in 257 blocks
==11605==         suppressed: 0 bytes in 0 blocks
==11605== Rerun with --leak-check=full to see details of leaked memory
==11605== 
==11605== For counts of detected and suppressed errors, rerun with: -v
==11605== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)

[arielb1]

Weird. Could you try and reduce that function?

[dpc]

I tried, but it it's highly coupled with the rest of the code, and I'm very short on time.

[steveklabnik]

Without a reproduction, this is going to be basically impossible to fix.

[dpc]

I don't think I'll be able to minimze this, so I'm closing.

[rprichard]

@dpc I reduced your code and filed #26468.

[dpc]

@rprichard : You're awesome!

[dpc]

The original issue is said to be fixed, but I'm experiencing it on the same code.