locate the memory adress
-
good morning, all Is there a way to locate certain memory address in app during the debug? say, I wanna find out 0x00FE55A0 is using by who? the reason is memory leak, I kinda know which class is leaking, but I couldn't see where exactly it is, there is FE5420 is using by m_pValid, but it got deleted when it close down. so the FE55A0 should be somwhere near by, but I never really find it. thanks for your time!
-
good morning, all Is there a way to locate certain memory address in app during the debug? say, I wanna find out 0x00FE55A0 is using by who? the reason is memory leak, I kinda know which class is leaking, but I couldn't see where exactly it is, there is FE5420 is using by m_pValid, but it got deleted when it close down. so the FE55A0 should be somwhere near by, but I never really find it. thanks for your time!
Hello, You can use the Visual Leak Detector[^] to trace down those pesky bugs and then eliminate them! Good hunt! ;) Behind every great black man... ... is the police. - Conspiracy brother Blog[^]
-
good morning, all Is there a way to locate certain memory address in app during the debug? say, I wanna find out 0x00FE55A0 is using by who? the reason is memory leak, I kinda know which class is leaking, but I couldn't see where exactly it is, there is FE5420 is using by m_pValid, but it got deleted when it close down. so the FE55A0 should be somwhere near by, but I never really find it. thanks for your time!
You can set a breakpoint on a memory address such that the application will break when the data at the specified address changes. Then it will show you what line of code just caused that change. You can do this by using the breakpoints dialog and then go to the data tab and enter your address in the edit block.
-
You can set a breakpoint on a memory address such that the application will break when the data at the specified address changes. Then it will show you what line of code just caused that change. You can do this by using the breakpoints dialog and then go to the data tab and enter your address in the edit block.
Thanks for your reply. I have problem setting them up, it has message box says "Cannot set the breakpoint when "0x00FE55A0" (length: 1)changed". not sure why, It should be the valid adreee, because it's the leak report says 1305 bytes leak from. and I could see the 0x00FE54D0 in somewhere....thank you!
-
Thanks for your reply. I have problem setting them up, it has message box says "Cannot set the breakpoint when "0x00FE55A0" (length: 1)changed". not sure why, It should be the valid adreee, because it's the leak report says 1305 bytes leak from. and I could see the 0x00FE54D0 in somewhere....thank you!
I would go with the other suggestion then. I am not sure why that error would come up. I tried it myself on my platform and I was able to set the break point. Since you have an idea where/when the code is changing, you could try to watch it in the memory window. Just press the memory button on the debug toolbar (when you are in debug) and then type the address of the memory location that you want to watch. You can then step through the code until your address changes.
-
I would go with the other suggestion then. I am not sure why that error would come up. I tried it myself on my platform and I was able to set the break point. Since you have an idea where/when the code is changing, you could try to watch it in the memory window. Just press the memory button on the debug toolbar (when you are in debug) and then type the address of the memory location that you want to watch. You can then step through the code until your address changes.