Active Topics 
Memberlist 
Calendar 
Search 
Help
Register 
Login |
Active Topics Memberlist Calendar Search Help |
| Register Login |
 One Stop Testing Forum : Software Testing @ OneStopTesting : Test Plans @ OneStopTesting |
|
  |
| Author | Message |
|
mangai166
Newbie 
Joined: 05Jun2008 Online Status: Offline Posts: 1 |
   Topic: BUG FATALPosted: 08Jun2008 at 10:49pm |
|
WHAT WE SHOULD EXPLAIN 4 THE QUEST...bug FATAL U HV CME ACROSS
Post Resume: Click here to Upload your Resume & Apply for Jobs |
|
 IP Logged |
|
|
lawrence
Groupie 
Joined: 22Nov2007 Location: India Online Status: Offline Posts: 73 |
Posted: 09Jun2008 at 8:11am |
|
If you had come across 'bug fatal', then explain it. Otherwise simply say 'I have not come across bug fatal so far'.
|
|
|
IP Logged |
|
|
cprasenjit26
Senior Member 
Joined: 14May2009 Location: India Online Status: Offline Posts: 151 |
Posted: 21Jul2009 at 8:18pm |
|
Fatal error handling is patchy and flaky. It's very easy to throw a fatal error, put up a message box, and then receive a Windows message containing yet more socket data. The MessageBox message loop then dispatches that message automatically and the back end is called reentrantly. Chaos ensues. Solution: the fatal error behaviour should be much more robust. Close all sockets the instant a fatal error occurs; also set some global flags that prevent action messages from having any back end effect.
-------------------------------------------------------------------------------
|
|
|
IP Logged |
|
| |
||
Forum Jump |
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot delete your posts in this forum You cannot edit your posts in this forum You cannot create polls in this forum You cannot vote in polls in this forum |
|
© Vyom Technosoft Pvt. Ltd. All Rights Reserved.
Topic: BUG FATAL