enums, 2005, and the debugger

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Peter Oliphant - 15 Nov 2005 16:20 GMT

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...

Reply to this Message

Tarek Madkour [MSFT] - 23 Nov 2005 23:43 GMT

> Not a big deal, but it looks like the runtime debugger 'inspects'
> (e.g., Autos window) user-defined enum's as having <undefined value>,
[quoted text clipped - 4 lines]
> 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,

Signature

Tarek Madkour, Visual C++ Team
This posting is provided "AS IS" with no warranties, and confers
no rights.

Reply to this Message

Peter Oliphant - 28 Nov 2005 16:45 GMT

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==]

>> Not a big deal, but it looks like the runtime debugger 'inspects'
>> (e.g., Autos window) user-defined enum's as having <undefined value>,
[quoted text clipped - 9 lines]
>
> Thanks,

Reply to this Message

Tarek Madkour [MSFT] - 30 Nov 2005 18:15 GMT

> 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,

Signature

Tarek Madkour, Visual C++ Team
This posting is provided "AS IS" with no warranties, and confers
no rights.

Reply to this Message

Peter Oliphant - 30 Nov 2005 18:36 GMT

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==]

>> 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?
[quoted text clipped - 6 lines]
>
> Thanks,

Reply to this Message

Tarek Madkour [MSFT] - 30 Nov 2005 23:06 GMT

> 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,

Signature

Tarek Madkour, Visual C++ Team
This posting is provided "AS IS" with no warranties, and confers
no rights.

Reply to this Message

Rate this thread:

enums, 2005, and the debugger

Free Magazines