Yes, definitely in the realm of undefined return value. Any decent compiler should have whined loudly that not all code paths return a value. It's important to respect such warnings from your compiler.
Dan is probably on the right track for what is going on. The code is probably expecting that the last value on the stack represents the return value. Depending on the ABI or the platform, it may always be the leftmost (or rightmost) parameter.
-Jason
Recent comments
10 sec ago
2 hours 55 min ago
2 hours 55 min ago
13 hours 9 min ago
14 hours 37 min ago
14 hours 37 min ago
14 hours 37 min ago
21 hours 54 min ago
2 weeks 3 days ago
4 weeks 4 days ago