Cryptic Names in Debug Call Stack

Cryptic Names in Debug Call Stack

Posted by: brett.ossman on 4 November 2021, 6:58 am EST

• 

  brett.ossman

  • Post Options:
  • Link
    Copy

  Posted 4 November 2021, 6:58 am EST

  Trying to figure out which functions are being called, and possibly parameters in the following call stack. Note the cryptic names (see the square symbols). Where do the function names come from?

  C1.Win.C1FlexGrid.4.dll!C1.Win.C1FlexGrid.C1FlexGrid.[b]* "‚a(int row, int col, object data)"
  

  [/b] Unknown
  
  C1.Win.C1FlexGrid.4.dll!C1.Win.C1FlexGrid.C1FlexGrid.‡a(C1.Win.C1FlexGrid.CellRange rg, int min, int max = 20, object data = null) Unknown
  
  C1.Win.C1FlexGrid.4.dll!C1.Win.C1FlexGrid.C1FlexGrid.†a(C1.Win.C1FlexGrid.CellRange rg, bool vert, bool horz = true) Unknown
  
  C1.Win.C1FlexGrid.4.dll!C1.Win.C1FlexGrid.C1FlexGrid.„a(int row, int col) Unknown
  
  C1.Win.C1FlexGrid.4.dll!C1.Win.C1FlexGrid.C1FlexGrid.GetMergedRange(int row = 1, int col = 53, bool clip = true) Unknown
  
  C1.Win.C1FlexGrid.4.dll!C1.Win.C1FlexGrid.C1FlexGrid.Invalidate(C1.Win.C1FlexGrid.CellRange rg) Unknown
  
  C1.Win.C1FlexGrid.4.dll!C1.Win.C1FlexGrid.C1FlexGridBase.OnGridChanged(object sender, C1.Win.C1FlexGrid.GridChangedEventArgs e = {C1.Win.C1FlexGrid.GridChangedEventArgs}) Unknown
  
  C1.Win.C1FlexGrid.4.dll!C1.Win.C1FlexGrid.C1FlexGrid.OnGridChanged(object sender, C1.Win.C1FlexGrid.GridChangedEventArgs e) Unknown

  EnRoute.Common.UI.dll!EnRoute.Common.UI.Controls.DoubleBufferC1FlexGrid.OnGridChanged(Object sender = {a.a}, C1.Win.C1FlexGrid.GridChangedEventArgs e = {C1.Win.C1FlexGrid.GridChangedEventArgs}) Line 280 Basic

• 

  wknauf

  • Post Options:
  • Link
    Copy

  Posted 5 November 2021, 4:48 am EST

  Hi Brett,

  that’s probably caused by some obfuscation tool ;-).

  In case you don’t already know it: if you need to take a look at the internals of the C1FlexGrid dll, you could use tools like ILSpy https://github.com/icsharpcode/ILSpy. But it is hard to read due to the obfuscation.
  
  Recent Visual Studio versions also provide a limited decompilation support.

  Best regards

  Wolfgang

• 

  brett.ossman

  • Post Options:
  • Link
    Copy

  Posted 5 November 2021, 6:48 am EST

  Thanks

  Yeah, I tried various options in Visual Studio, including decompiling, and couldn’t get a function or an indication of what the call was trying to do at that point. MAYBE, I could search for the parameter signature in Grape City’s class documentation and find something. We’ll see.

• 

  avnish.kumar

  

  • Post Options:
  • Link
    Copy

  Posted 8 November 2021, 12:44 am EST

  Hi,

  C1 libraries are obfuscated due to security purposes. You will be able to clearly see the names of non-obfuscated public members.
  
  If you are facing any specific issue, please let us know and we will help you accordingly.

  Regards
  
  Avnish