enums, 2005, and the debugger

[Peter Oliphant]

Not a big deal, but it looks like the runtime debugger 'inspects' (e.g.,
Autos window) user-defined enum's as having <undefined value>, even though
the execution seems to recognize their value just fine.

Is this normal, or is there something 'wrong' with my enum somehow (don't
think that's possible); or best yet, is it possible to make the debugger
recognize enum's and show its enum (alias) name when inspecting?

[==P==]

PS - I'm using VS c++.NET 2005 Express...

 

[Tarek Madkour [MSFT]]

Not a big deal, but it looks like the runtime debugger 'inspects'
(e.g., Autos window) user-defined enum's as having <undefined value>,
even though the execution seems to recognize their value just fine.

Is this normal, or is there something 'wrong' with my enum somehow
(don't think that's possible); or best yet, is it possible to make the
debugger recognize enum's and show its enum (alias) name when
inspecting?

Yes, this is a known issue with debugging *managed* code using the VS
debugger. It should work for native code, though.

Thanks,

 

[Peter Oliphant]

Thanks Tarek!

You say this is a 'known issue'. That's not the same as saying it's a bug
needing fixing. Is this something that is planned to be fixed? After all,
isn't the push away from native code and towards (/clr) managed code? If so,
I would think that any disadvantage that managed code has should be
remedied, yes? : )

[==P==]

 

[Tarek Madkour [MSFT]]

You say this is a 'known issue'. That's not the same as saying it's a
bug needing fixing. Is this something that is planned to be fixed?

Yes, we are aware of several native / managed inconsistencies in the
debugger that we are currently developing a plan to remedy.
Unfortunately, the scope of the work is beyond a few minor bug fixes.
Several components need to be changed (and possible shared) in order to
achieve success.

Thanks,

 

[Peter Oliphant]

Hi Tarek,

I figured it wouldn't be an easy or quick fix. But it's good to know it is
considered a problem to be fixed at some point.

When it is fixed, my 'dream case' would be that it didn't just show the
value for an enum, but the variable name equivalent (which is, after all,
one of the main reasons for using an enum over just establishing a
convention based on int value). Is this the plan? : )

[==P==]

 

[Tarek Madkour [MSFT]]

When it is fixed, my 'dream case' would be that it didn't just show
the value for an enum, but the variable name equivalent (which is,
after all, one of the main reasons for using an enum over just
establishing a convention based on int value). Is this the plan? : )

That would be my expectation of the feature as well

Thanks,