I want to print out the value of 2nd and 3rd parameters for the line number 151

They supposed to be address, but im not able to display them, look at the output window, how do i properly display them ?

Looks like OutputDebugStringA merely prints string (without format specifier available). To display memory address, you have to convert it to hexadecimal numbers.

For example in C:

actually i tried printf, nothing visible(no error either).

Try this,
sprintf(stderr, "%x\r\n",&pbmpinf);


Alternative longer,
char szMsg[32];
snprintf(szMsg, sizeof(szMsg), "%x\r\n",&pbmpinf);
OutputDebugStringA (szMsg);

Wow, still have people doing C.

To get the address of that PBitmapInfo, have you try , rather than ?

I haven't touch C++ for more than a decade, I might have got the operator precedence wrongly.

What's the definition of PBitmapInfo and PBitmapBits? If these are addresses (or pointers), then you should use be using printf("%x", pFrameData->PBitmapInfo).

Using &pFrameData->PBitmapInfo would mean, "address of pFrameData->PBitmapInfo", i.e. address of an address.

*pFrameData->PBitmapInfo would then be "content of pFrameData->PBitmapInfo".

Or just save your headache and use a debugger, put a breakpoint on that line, and see the value in memory.

ya, im backing off, what i was doing is making dll and plug into unity, dll do not really give you error, it will just crash, i think i need to do 1 step at a time.

whole picture is, i want to use capture card sdk, capture bitmap(the question you ask what are those, they are pointer returned by a capture call back after 1 frame has been captured), then in unity, what supposed to happen is call the dll, unity create texture, pass texture reference into c++ native dll, then the native dll fill the texture with bitmap data(using opengl).

Why doing it outside unity ? cause we can only use main thread to do certain things, and i want the capture to happen as fast as possible, so it need to be offload to other thread, and that can only work outside unity.

That sounds like A LOT OF WORK
I imagine there will be crap loads of bitmaps that will be captured. It might take up a lot of resources just to dump out the data.
Anyway, if you're doing a dll, the only option probably is to write to external files.

I did something similar to debug something - modified and custom compiled Python's core dll to dump Python opcodes to a separate file. If I'm not mistaken, DLLs can't spin off consoles to print data.

nope, file base not acceptable. technically i have done something similar but capture bmp in external desktop app, use socket pass them into unity(within same pc), then unity upload to gpu (means convert to texture) in the main thread, the maximum it can go is around 200 FullHD(32bit) bitmap per second, bandwidth wise is 1920x1080x4(32bit to 4 byte)x200 bmp = 1.65 gigabyte per second.

normal hdd cant write that much per second, and if use SSD, the SSD will die within a year or so(cause SSD have limited writes per cell), and i am trying to see if i use multithread, wanna push that limit to another few times higher.

PCIE 4.0x16 bandwidth is ~32Gigabyte per second. i am not greedy, if can achieve 10GB(~1200 full hd bmp per second), im very happy d.

Oooh.. very interesting approach! I haven't studied much how on how to use gpu (nor unity). That will definitely go into my to-study list.

lol now im forcing myself to learn c/c++, i think i venture into a dark area that if i cant help myself, nobody can.

Ignore my last comment. Google result shows -> indeed has higher precedence than &.