ESE is an embedded / ISAM-based database engine, that provides rudimentary table and indexed access. However the library provides many other strongly layered and and thus reusable sub-facilities as well: A Synchronization / Locking library, a Data-structures / STL-like library, an OS-abstraction layer, and a Cache Manager, as well the full blown database engine itself
MIT License
819
stars
62
forks
source link
Debugging your ESE application (or even - ESE-based Windows services) with the ESE debugger extension. #26
Debugging your ESE application (or even - ESE-based Windows services) with the ESE debugger extension.
This could go on and on ... but to start we at least need to cover the basics of how to use windbg.exe/cdb.exe, what the ESE debugger extension is, and a few basic ESE debugger commands.
Then later we would cover more advanced ESE debugger commands, that accomplish specific purposes. You can inspect a great many things in a process with our debugger extensions - how our memory is being utilized, finding the longest running transaction, seeing if we have a hung IO operation (disk not returning), and many many more.
Feel free to respond to the issue to:
Suggest specific debug scenarios,
Or questions you might have of an active process.
This issue will be closed when basics and a few extra scenarios are documented, and I will spin anything left in comments into new issues.
Debugging your ESE application (or even - ESE-based Windows services) with the ESE debugger extension.
This could go on and on ... but to start we at least need to cover the basics of how to use windbg.exe/cdb.exe, what the ESE debugger extension is, and a few basic ESE debugger commands.
Then later we would cover more advanced ESE debugger commands, that accomplish specific purposes. You can inspect a great many things in a process with our debugger extensions - how our memory is being utilized, finding the longest running transaction, seeing if we have a hung IO operation (disk not returning), and many many more.
Feel free to respond to the issue to:
This issue will be closed when basics and a few extra scenarios are documented, and I will spin anything left in comments into new issues.
Up-vote this issue if it is of interest.