Author Topic: JIT debugger  (Read 1479 times)

Offline everSome

  • Multiple posting newcomer
  • *
  • Posts: 14
JIT debugger
« on: February 19, 2022, 06:56:58 pm »
I've come to understand that CodeBlocks uses Dr Mingw as its JIT debugger. But I'm wondering how useful that is considering that strip is run against all the .exe and .dll files in output31_64.

Offline BlueHazzard

  • Developer
  • Lives here!
  • *****
  • Posts: 3221
Re: JIT debugger
« Reply #1 on: February 19, 2022, 10:10:35 pm »
useless i suppose....
i asked killerbot to not strip the nightlies, but i did not get any response

Offline AndrewCot

  • Lives here!
  • ****
  • Posts: 576
Re: JIT debugger
« Reply #2 on: February 20, 2022, 12:34:11 am »
everSome, What are you trying to do?

The doc I posted for you to follow a while ago has info on debugging codeblocks, my post was:
https://forums.codeblocks.org/index.php/topic,24814.msg169333.html#msg169333

Offline everSome

  • Multiple posting newcomer
  • *
  • Posts: 14
Re: JIT debugger
« Reply #3 on: February 21, 2022, 02:55:51 am »
What are you trying to do? I'm poking around the edges of compiling CodeBlocks with just the MSYS2 tool chains installed on my system. Not being enamored with the out of band binaries existing in src/exchndl, I looked into what that's for. Turns out that MSYS2 has binary packages for Dr Mingw for the various MSYS2 environments. So I loaded these binary packages and compiled against them. For instance, the UCRT64 package's url is:
https://packages.msys2.org/package/mingw-w64-ucrt-x86_64-drmingw?repo=ucrt64
This supplies exchndl.dll and mgwhelp.dll
The dbgcore.dll, dbghelp.dll, and symsrv.dll are distributable Microsoft components, but more up to date versions can be had directly from them if one wishes. The mgwhelp.dll is used to access dwarf (something like Debug With Arbitrary Record Format) information whereas dbgcore/dbghelp stuf is used to access Microsoft's PDB debug information files. symsrv.dll is used to access Microsoft's publicly exposed Symbol server, and symsrv.yes keeps the damn thing from trying to dialog with the user on startup. I'm just an old fart with time on his hands! But I'm learning. It just seemed odd to me that there is this elaborate construction to provide a postmortem dump but not feed it any debugging info. Just wondering if there was a back door to such info, but I guess not. Unwinding a stack usually needs all the help it can get.

Offline ollydbg

  • Developer
  • Lives here!
  • *****
  • Posts: 5567
  • OpenCV and Robotics
    • Chinese OpenCV forum moderator
Re: JIT debugger
« Reply #4 on: July 30, 2022, 04:33:11 pm »
Hi, everSome,

Do you have the latest drmingw 0.9.5 working with the current SVN head of C::B?

See this post:

error alert message when using ThreadSearch Plugin

It looks like I have some problem with the latest version of drmingw.
If some piece of memory should be reused, turn them to variables (or const variables).
If some piece of operations should be reused, turn them to functions.
If they happened together, then turn them to classes.