I’m getting this message in WinDbg.
What’s the easiest way to find the offending code?
I can’t work out how to generate a map file from WDK build. I’ve tried
/Fm in the sources but no good. I’m assuming this will list code
segments for each routine.
Regards,
–
Mark McDougall, Engineer
Virtual Logic Pty Ltd, http:
21-25 King St, Rockdale, 2216
Ph: +612-9599-3255 Fax: +612-9599-3266</http:>
Try: “LINKER_FLAGS=-map -mapinfo:exports” in the sources file.
“Mark McDougall” wrote in message news:xxxxx@ntdev…
> I’m getting this message in WinDbg.
>
> What’s the easiest way to find the offending code?
>
> I can’t work out how to generate a map file from WDK build. I’ve tried
> /Fm in the sources but no good. I’m assuming this will list code
> segments for each routine.
>
> Regards,
>
> –
> Mark McDougall, Engineer
> Virtual Logic Pty Ltd, http:
> 21-25 King St, Rockdale, 2216
> Ph: +612-9599-3255 Fax: +612-9599-3266
></http:>
David Craig wrote:
Try: “LINKER_FLAGS=-map -mapinfo:exports” in the sources file.
Thanks! Worked a treat!
Regards,
–
Mark McDougall, Engineer
Virtual Logic Pty Ltd, http:
21-25 King St, Rockdale, 2216
Ph: +612-9599-3255 Fax: +612-9599-3266</http:>