locked
Generated assembly loaded at debug-time RRS feed

  • Question

  • Hi,

    In a debug session with VS 2010, by running 

    AppDomain.CurrentDomain.GetAssemblies
    

    I can see an esoteric assembly name (something like "gm5epd1v, Version=4.0.0.0, Culture=neutral, PublicKeyToken=null") among the loaded assemblies. It changes for each run so I can assume it's generated but it's not flagged as dynamic. Any idea about what it can be ? 

    Thanx in advance. 

     

     


    Searching... wondering...
    Friday, August 12, 2011 10:34 AM

Answers

  • I do not know if this a feasible method for you:
    Probably it helps, trying to get more info about the loaded assembly with sos.dll, which you can load into Visual studio 2010 through Immediate Window (in Project Properties "Enable unmanaged code debugging must be enabled").
    .load sos
    Then hopefully you get all loaded assemblies, including the "esoteric" ones through:
    !dumpdomain
    --------------------------------------
    System Domain:      65353478
    LowFrequencyHeap:   65353784
    .....
    Assembly:           001309b0 [pjacx3ws, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null]
    ClassLoader:        0013e5a8
    SecurityDescriptor: 00130920
      Module Name
    00654d0c            pjacx3ws, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null
    .....
    !dumpmodule 00654d0c
    Name:       pjacx3ws, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null
    Attributes: PEFile
    Assembly:   001309b0
    LoaderHeap:              00000000
    TypeDefToMethodTableMap: 007109a4
    TypeRefToMethodTableMap: 007109c0
    MethodDefToDescMap:      00710a24
    FieldDefToDescMap:       00710a88
    MemberRefToDescMap:      00710ab0
    FileReferencesMap:       00710bb0
    AssemblyReferencesMap:   00710bb4
    MetaData start address:  007407dc (4356 bytes)
    ...
    Then you might get in Memory Window following 007407dc (MetaData) some info, which could give you a hint.
    ....
    0x00740D8C  00000000 ...  .....<Module>.pj
    0x00740D9C  33786361 ...  acx3ws.dll.XmlSe
    0x00740DAC  6c616972 ...  rialization ...
    ...

    No warranty  (Vista32)
    With kind regards

    • Marked as answer by eryang Monday, August 22, 2011 7:52 AM
    Friday, August 12, 2011 4:18 PM

All replies

  • I do not know if this a feasible method for you:
    Probably it helps, trying to get more info about the loaded assembly with sos.dll, which you can load into Visual studio 2010 through Immediate Window (in Project Properties "Enable unmanaged code debugging must be enabled").
    .load sos
    Then hopefully you get all loaded assemblies, including the "esoteric" ones through:
    !dumpdomain
    --------------------------------------
    System Domain:      65353478
    LowFrequencyHeap:   65353784
    .....
    Assembly:           001309b0 [pjacx3ws, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null]
    ClassLoader:        0013e5a8
    SecurityDescriptor: 00130920
      Module Name
    00654d0c            pjacx3ws, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null
    .....
    !dumpmodule 00654d0c
    Name:       pjacx3ws, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null
    Attributes: PEFile
    Assembly:   001309b0
    LoaderHeap:              00000000
    TypeDefToMethodTableMap: 007109a4
    TypeRefToMethodTableMap: 007109c0
    MethodDefToDescMap:      00710a24
    FieldDefToDescMap:       00710a88
    MemberRefToDescMap:      00710ab0
    FileReferencesMap:       00710bb0
    AssemblyReferencesMap:   00710bb4
    MetaData start address:  007407dc (4356 bytes)
    ...
    Then you might get in Memory Window following 007407dc (MetaData) some info, which could give you a hint.
    ....
    0x00740D8C  00000000 ...  .....<Module>.pj
    0x00740D9C  33786361 ...  acx3ws.dll.XmlSe
    0x00740DAC  6c616972 ...  rialization ...
    ...

    No warranty  (Vista32)
    With kind regards

    • Marked as answer by eryang Monday, August 22, 2011 7:52 AM
    Friday, August 12, 2011 4:18 PM
  • We temporarily mark a reply since the thread idle for a long time, please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.


    Eric Yang [MSFT]
    MSDN Community Support | Feedback to us
    Get or Request Code Sample from Microsoft
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    Monday, August 22, 2011 7:52 AM
  • Thanx for your answer and sorry for having been long to come back but I was on vacation.

    I gonna try that and give you the feedback.

    Regards.


    Searching... wondering...
    Saturday, August 27, 2011 1:46 PM