Hi, Jb,
Thanks for the checking.
I made some changes in MemberReference.DeclaringType:
public virtual TypeReference DeclaringType {
get { return declaring_type; }
set
{
//wicky.patch.start: avoid recursive declaringtype of
some obfuscated assemblies,
//currently only one level checking
if (value != null && value.DeclaringType == this)
{
return;
}
//wicky.patch.end
declaring_type = value;
}
}
Not sure whether it's a best way, but I can load and browse the
assembly now.
Regards
Wicky
On Dec 9, 6:22 pm, Jb Evain <[email protected]> wrote:
> Well, that sounds like normal to me, the assembly has two TypeRef
> declaring each other as their DeclaringType.
>
> I can't do much more here, they're not even references in the object tree.
>
>
>
> On Thursday, December 9, 2010, Wicky <[email protected]> wrote:
> > Hi, Jb,
>
> > On Dec 8, 8:16 pm, Jb Evain <[email protected]> wrote:
> >> And that's fixed in master.
>
> > I just tried the latest version, it's ok to get all type references,
> > but when reading FullName of type reference [0x01000026], Cecil gives
> > stackoverflow again.
>
> > Regards
> > Wicky
>
> > --
> > --
> > mono-cecil- Hide quoted text -
>
> - Show quoted text -
--
--
mono-cecil
