crosire
crosire
On 1: Jup (see also #8). This would require going through the import address table (which blink already does anyway) and load all the PDBs for imported libraries too, instead...
Technically blink makes use of a lot of the information provided by `/ZI`. So there are silimarities. But this projected started back when EnC was still much more limited (it...
It does not work on code for which there are no symbols in the application PDB. These are used to determine function addresses etc. in the loaded image, so are...
There are two ways DLLs can be loaded, either via a static import or dynamically via `LoadLibrary`. The first case can be covered by retrieving the PDB info here: https://github.com/crosire/blink/blob/9ca9e5c91c4cf5e23cefc7ed3c5489817ea34261/source/blink.cpp#L55...
Added an untested, experimental branch which loads symbols for statically linked DLLs: ~https://github.com/crosire/blink/tree/dlls~ EDIT: This is now in master.
blink does not currently support dynamically loaded DLLs.
It doesn't currently. It would be possible to figure out all the source files affected in theory (that information is stored in the PDB and blink already reads that, it...
See the following (this list also contains header files, but blink currently filters it for *.cpp files only): https://github.com/crosire/blink/blob/55f2534f1933af0c70eeab5ce106fb888e51c0cc/source/blink.cpp#L131
Nope, they are all in. It is a lot of data.
Proof of concept is in the `headers` branch. It will compile all source files which include the modified header file.