Click here to Skip to main content
15,889,931 members
Home / Discussions / C / C++ / MFC
   

C / C++ / MFC

 
Questionscrollbar doesnt work Pin
aangerma7-Oct-10 0:59
aangerma7-Oct-10 0:59 
AnswerRe: scrollbar doesnt work Pin
Dave Calkins7-Oct-10 2:54
Dave Calkins7-Oct-10 2:54 
QuestionRestrict Writing to USB Pin
Subrat Patnaik7-Oct-10 0:49
Subrat Patnaik7-Oct-10 0:49 
AnswerRe: Restrict Writing to USB Pin
«_Superman_»7-Oct-10 0:53
professional«_Superman_»7-Oct-10 0:53 
QuestionPlease help me for debug information. Pin
Le@rner7-Oct-10 0:39
Le@rner7-Oct-10 0:39 
AnswerRe: Please help me for debug information. Pin
Richard MacCutchan7-Oct-10 1:11
mveRichard MacCutchan7-Oct-10 1:11 
AnswerRe: Please help me for debug information. Pin
Alan Balkany7-Oct-10 4:48
Alan Balkany7-Oct-10 4:48 
QuestionPassing parameter in worker thread Pin
learningvisualc7-Oct-10 0:35
learningvisualc7-Oct-10 0:35 
AnswerRe: Passing parameter in worker thread Pin
«_Superman_»7-Oct-10 0:44
professional«_Superman_»7-Oct-10 0:44 
GeneralRe: Passing parameter in worker thread Pin
learningvisualc7-Oct-10 1:03
learningvisualc7-Oct-10 1:03 
GeneralRe: Passing parameter in worker thread Pin
«_Superman_»7-Oct-10 1:11
professional«_Superman_»7-Oct-10 1:11 
GeneralRe: Passing parameter in worker thread Pin
bleedingfingers7-Oct-10 1:11
bleedingfingers7-Oct-10 1:11 
QuestionDisable All Breakpoints In Visual C++ 6.0 Pin
timb756-Oct-10 23:14
timb756-Oct-10 23:14 
AnswerRe: Disable All Breakpoints In Visual C++ 6.0 Pin
bleedingfingers7-Oct-10 0:02
bleedingfingers7-Oct-10 0:02 
GeneralRe: Disable All Breakpoints In Visual C++ 6.0 Pin
timb757-Oct-10 0:11
timb757-Oct-10 0:11 
AnswerRe: Disable All Breakpoints In Visual C++ 6.0 Pin
Moak7-Oct-10 0:49
Moak7-Oct-10 0:49 
GeneralRe: Disable All Breakpoints In Visual C++ 6.0 Pin
bleedingfingers7-Oct-10 1:37
bleedingfingers7-Oct-10 1:37 
GeneralRe: Disable All Breakpoints In Visual C++ 6.0 Pin
Moak7-Oct-10 2:05
Moak7-Oct-10 2:05 
QuestionRe: Disable All Breakpoints In Visual C++ 6.0 Pin
bleedingfingers7-Oct-10 2:36
bleedingfingers7-Oct-10 2:36 
AnswerRe: Disable All Breakpoints In Visual C++ 6.0 Pin
Moak7-Oct-10 4:15
Moak7-Oct-10 4:15 
QuestionMemory usage Pin
sonualex6-Oct-10 21:15
sonualex6-Oct-10 21:15 
AnswerRe: Memory usage Pin
Cedric Moonen6-Oct-10 21:29
Cedric Moonen6-Oct-10 21:29 
AnswerRe: Memory usage [modified] Pin
Aescleal6-Oct-10 22:51
Aescleal6-Oct-10 22:51 
QuestionRe: Memory usage Pin
sonualex12-Oct-10 23:37
sonualex12-Oct-10 23:37 
QuestionProgram crashes, log entries and map files Pin
Interrobang6-Oct-10 6:58
Interrobang6-Oct-10 6:58 
Greetings!

Our application is built in MS Visual C++ 6. I'm running Windows XP Pro, and our customer is running Windows Server 2003.

Our customer has reported rare instances in which our program has crashed, but the only way he knows about it is entries that appeared in the Windows System event log, as copies of the popup window that was displayed to the user. The source of the log entry is given as "Application Popup". The instruction address in one of the messages is 0x075c0001.

We do not currently have map files for our application. I thought that we should, and I started experimenting with them. For my first experiment, I forced a divide by zero error in the application's main executable, and rebuilt it with the correct settings to generate a map file. My application duly crashed, and shortly thereafter a popup message appeared telling me that an instruction at address 0x5f801088 referenced memory at 0x00000004. In my applicaton event log, I found an event reporting that my application faulted in its executable file, at address 0x0001fb3a. Using instructions I found on the Web, I was able to use the map file to go from address 0x0001fb3a to the correct line in my code. There was a second entry in the Windows event log, this time in the system log, repeating what the popup had told me.

I then repeated the experiment with one of the DLLs our application uses, and again I was successful, using the address found in the entry in the Windows application log. There was one difference here, though: I did not get the popup complaining about an instruction that failed, and I did not get an entry in the system log.

On our customer's system, the situation is the opposite: We have entries in the system log, but not in the application log.

The addresses of instructions given in the map file are all relatively low, low enough to contain the address given in the application event log, 0x0001fb3a. I cannot be positive that the address given in the popup message and the system log is referring to the same instruction, since it is quite possible that something else in the application is trying to use an object that just crashed and burned. But the high address number leads me to believe that it is using a different reference point. Maybe it is based on the raw address in the processor instead of the application's address space, or some such thing.

Can anyone give a theory about why our customer might see an error in the system log reporting a bad instruction, but no corresponding error in the application log? Can anyone point me to instructions on how to map the address in the system log to an entry in a map file?

Thank you very much!

RobR

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Praise Praise    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.