C# JIT Decompilation Tips using WinDBG

Поділитися
Вставка
  • Опубліковано 8 вер 2024

КОМЕНТАРІ • 10

  • @LevelUppp
    @LevelUppp  3 роки тому +1

    Do you use WinDbg? If yes then what's your typical use case?

    • @Adeith
      @Adeith 3 роки тому +2

      I have been meaning to learn it but haven't found a reason yet. Really looking forward to more videos on it.

    • @1off271
      @1off271 3 роки тому +1

      Yes, only for dump investigations

    • @codeyoga
      @codeyoga 3 роки тому

      I do use it to analyse CLR Dumps related to process hangs / crashes / OOM exceptions.

    • @nemanjasimic8895
      @nemanjasimic8895 3 роки тому

      Great videos, I've just found out about your channel.
      I am using WinDbg for post mortem analysis, investigating dumps for memory leaks, race conditions etc.
      Sometimes when services are too complex, and GC is running all the time, WinDbg cannot read all parts of memory dump because GC was holding some parts at the time it was created.
      In such a case I am using System.Diagnostics namespace. I would write a little console app for my use case and investigate dump through coding, I find it very useful when WinDbg has troubles.