Simulating a Memory issue
Dear Experts
One of our testers reported an internal error after opening all accounts on our application written C as front end and Oracle as backend. This internal error caused an immediate shutdown of the application and the accounts could not be opened.
In order to simulate this issue , I ran the session with exactly the same criterias as the tester did and debugged the function the application calls when it reaches the summary screen but did not find any discrepancies and I was successful.
The tester gets this internal error anytime , its not specific. I have done the code review of the functions which are called when it reaches the summary screen but did not find any dangling pointer issue.
Please advice me how do i tackle such issues.
What must be done in order to simulte such error.
Your suggestions will be extremely helpful
Ronan
One of our testers reported an internal error after opening all accounts on our application written C as front end and Oracle as backend. This internal error caused an immediate shutdown of the application and the accounts could not be opened.
In order to simulate this issue , I ran the session with exactly the same criterias as the tester did and debugged the function the application calls when it reaches the summary screen but did not find any discrepancies and I was successful.
The tester gets this internal error anytime , its not specific. I have done the code review of the functions which are called when it reaches the summary screen but did not find any dangling pointer issue.
Please advice me how do i tackle such issues.
What must be done in order to simulte such error.
Your suggestions will be extremely helpful
Ronan
which operating system are you using?
Was the tester using a "release" build? If so, sometimes, they're different enough to cause problems. This is when logging becomes important. I would recommend enhancing the logging functionality within your code.
ASKER
cwwkie
its linux OS
guitarist yes testers are using a release build, please let me know more abt logging functionality
thank you
ronan
its linux OS
guitarist yes testers are using a release build, please let me know more abt logging functionality
thank you
ronan
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
cwwkie and guitaristx
Thanks for the valuable inputs. I am working on writing fflush and fprintf statements . will get back to you shortly
thanks for ur time
Ronan
Thanks for the valuable inputs. I am working on writing fflush and fprintf statements . will get back to you shortly
thanks for ur time
Ronan
When the program stops, does it just close normaly or does it print out any messages?
Bill
Bill
ASKER
Bill
When the program stops , it sends a message on to the screen that " Internal Error occured , press any key to initiate shutdown " when a tester presses any key , it terminates.
And now today our tester reported that , she did not receive any error that she received previously.
I am working on writing fflush and fprintf statemsnt so and will have the log generated in the current working directory in linux
I will get back to u guys,
Thanks all
Ronan
When the program stops , it sends a message on to the screen that " Internal Error occured , press any key to initiate shutdown " when a tester presses any key , it terminates.
And now today our tester reported that , she did not receive any error that she received previously.
I am working on writing fflush and fprintf statemsnt so and will have the log generated in the current working directory in linux
I will get back to u guys,
Thanks all
Ronan