RE: *weird* overflow error *after* API call; call works OK, but later simple steps fail
From: Yan-Hong Huang[MSFT] (yhhuang_at_online.microsoft.com)
Date: 05/19/04
- Next message: Gary Chang: "Re: Debug TRACE style output wihout leaving literal strings in binary"
- Previous message: Philip Warner: "*weird* overflow error *after* API call; call works OK, but later simple steps fail"
- In reply to: Philip Warner: "*weird* overflow error *after* API call; call works OK, but later simple steps fail"
- Next in thread: Bob Butler: "Re: *weird* overflow error *after* API call; call works OK, but later simple steps fail"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 19 May 2004 08:37:02 GMT
Hello Philip,
This problem is quite strange. I met a similar problem before when handling
one service request before. In that case, the root cause is some memory
chaos in customer's code. We finally found out the root cause by using
WinDBG and checking the address of each variable during the execution.
For your question, I think the memory address of qqq is overrided by some
function call, most possibly when returning from some function. In order to
troubleshoot it, assembly code, call stack, WinDBG are some necessary
tools. It is quite hard to tell exactly where the error lies based on the
limited information. You may also try to isolate the problem by simplying
the code first.
However, this issue is also related to one third party DLL code. It also
makes the problem complicated. For the time being, I suggest you submit one
service request to Microsoft.(You should have 2 free support incidents in
MSDN subscriber package) Our support engineer could help you isolate the
problem to see which component causes the error. If it is in Microsoft, we
will do our best to fix it. If it is related to that 3rd party DLL, you may
go ahead to contact that third party vendor for more information.
Thanks very much. If you have any more concerns on it, please feel free to
post here.
Best regards,
Yanhong Huang
Microsoft Community Support
Get Secure! ¨C www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.
- Next message: Gary Chang: "Re: Debug TRACE style output wihout leaving literal strings in binary"
- Previous message: Philip Warner: "*weird* overflow error *after* API call; call works OK, but later simple steps fail"
- In reply to: Philip Warner: "*weird* overflow error *after* API call; call works OK, but later simple steps fail"
- Next in thread: Bob Butler: "Re: *weird* overflow error *after* API call; call works OK, but later simple steps fail"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|