> > - in type_get_info, extend the types supported by
> also searching the lookup table for the pointers
> type.
> > the lookup table should contain pointee type and
> module of pointee. You could also extend step 1 by
> not adding a pointer that already exists.
> > A+
> does the attached (and qui
Pouech Eric DMI AEI CAEN a écrit :
Ok, I'll take a look at this, but if where shouldn't
be using two pointer types we should be using
SymGetTypeInfo in all cases?
the only (two things) you have to do are:
- if one cannot find the pointer type in the pointee's module, then create a
winedbg's type f
> Ok, I'll take a look at this, but if where shouldn't> be using two pointer types we should be using> SymGetTypeInfo in all cases?
the only (two things) you have to do are:
- if one cannot find the pointer type in the pointee's module, then create a winedbg's type for the pointer type and store t
--- Pouech Eric DMI AEI CAEN <[EMAIL PROTECTED]>
wrote:
> I don't think this patch should go in as it is:
> - I don't think it's a good idea to have two ways to
> express a pointer type in the debugger (one being
> the standard dbghelp's SymTagPointerType, the other
> one the new deref count you'
I don't think this patch should go in as it is:
- I don't think it's a good idea to have two ways to express a pointer type in the debugger (one being the standard dbghelp's SymTagPointerType, the other one the new deref count you've introduced). It would be better to add dynamic winedbg types (in
