SomeDude <> changed:

           What    |Removed                     |Added
                 CC|                            |

--- Comment #6 from SomeDude <> 2012-04-21 12:46:26 
PDT ---
(In reply to comment #5)
> Sorry for the confusion - I'm not used to assuming that breaking in a debugger
> could cause side-effects :)

Actually, on concurrent programming, it does, and the debugger is practically
useless, because you won't be able to see concurrent accesses. You should
really use traces.

Anyway, both test codes compile and run fine on my machine (2.059 Win32).
Should we close ?

Configure issuemail:
------- You are receiving this mail because: -------

Reply via email to