Thomas Tempelmann wrote:
On 2/17/06, Joseph J. Strout <[EMAIL PROTECTED]> wrote:
The bug appears to be in the socket event handling code: It
allows new incoming socket events to be processed immediately
instead of putting them into a queue and handling them only if
previous socket events have been handled.
Only if the new event is Error.
I wonder if Aaron, who would probably be responsible for this,
even agrees that this is a bug?
If you're seeing it with anything but Error, it would be. With
Error, it is not.
OK, since everyone that works at RS (or used to) is so certain that
there's no re-entry unless it's an Error, I'll not keep questioning
that for now unless I can prove it.
[snip]
The latest test case (v2.0) makes it very clear that overlapping occurs
even without threads or the error event being fired.
[jycozgss]
http://support.realsoftware.com/feedback/viewreport.php?reportid=jycozgss
1. Run the test case.
2. Overlapping occurs frequently.
3. Quit.
4. In the DataAvailable event, uncomment "#pragma BackgroundTasks False"
5. Run the test case again.
6. Overlapping no longer occurs.
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
