Why having a stackoverflow exception before the function is even executed?

Question

I wrote code that overrides object's Equals. I realized, after I wrote it, that I'm going to have StackOverFlowException since I didn't yet implemented the IEquatable interface to handle the last line of code. Yet, I run the code to see what happen, and some strange thing happen, you can see for yourself in the following image:

The breakpoint isn't even hittable at this moment, seems like the code is being used even before my program is run. Is it something that is done by the CLR ? Is it something else ?

Thanks for the help !

Your brakepoint will never be hit. It's white inside (not red and have warning on it), so the code does not match the running probram. Rebuild your solution. — Dovydas Šopa
– Dovydas Šopa, Commented May 11, 2016 at 6:49

Dmitrii Bychenko · Accepted Answer · 2016-05-11 07:03:32Z

2

The stack is exhausted (the very last straw that breaks camel's back) on

  if (ReferenceEquals(right, null))

probably, the stack doesn't have another 4 (8) bytes to store right. The actual reason seems to be at

  return Equals(right as Quality)

if right is of Quality type, the code is doomed to call Equals again and again

edited May 11, 2016 at 7:03

answered May 11, 2016 at 6:56

Dmitrii Bychenko

188k20 gold badges178 silver badges231 bronze badges

Sign up to request clarification or add additional context in comments.

3 Comments

Moti Berger Over a year ago

I know where the recursive part is, it can be shown by the mark next to that line. This isn't my question. The question is why the breakpoint was missed. I would expect that even if it is an endless recursive function, I would hit the breakpoint in the first call to Equals.

Dmitrii Bychenko Over a year ago

@Moti Berger: the stack is consuming, and in some point it, finally, got exhausted: stack can't allocate another 4/8 bytes. This final blow can occur at some random/weird point

Moti Berger Over a year ago

I understand that in an infinite recursive calling the stack eventually get exhausted, but for the exhaustion to happen, the function's code must run at least one time, so why the breakpoint wasn't hit. Something, which isn't my code, must have used the Equals function of the Quality type before my code even run ! My question is who used that function. The program crashed before it starts !

Collectives™ on Stack Overflow

Why having a stackoverflow exception before the function is even executed?

1 Answer 1

3 Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

3 Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related