The SerialPortStream project is very dependent on the Operating System and the Serial Drivers that are in use. For example, Prolific has shown issues when reading data, one driver didn't support the Break signal, another driver didn't return to say that the hardware buffer is empty.

I can't predict the kind of failure's you'll have before hand. Thus, if you find any issues, report them in either Discussions, or Issues. I will need to know the following information:
  • How do you recreate the issue?
  • Can you use a different driver version, or a different serial port? If possible, a 16550A physical UART should be checked, and if that's not possible (most computers don't come with a 16550A anymore), use an FTDI chipset and driver.

You should provide information about your test environment:
  • What is your Operating System?
  • Is it 64-bit or 32-bit?
  • Did you use the precompiled binaries (which version), or compile it yourself?

If you compiled the binaries yourself, you'll need to provide me everything you can:
  • The PDB file generated by your compilation (it must be a private PDB, generated using the Debug configuration)
  • The SVN revision which you used to compile the source. If you modified the source, even if it's just spacing, you should provide a copy of that, so I can debug.
  • You should provide a dump (a full dump, not a mini-dump) at the time of the failure. I can use this dump within the Windows WinDBG debugger.
  • The WinDBG needs the following libraries. For example, if you're using 64-bit .NET 4.0:
    • From the folder C:\Windows\Microsoft.NET\Framework64\v4.0.30319, grab the files
      • clr.dll
      • mscordacwks.dll
      • mscorwks.dll
      • SOS.dll

Last edited Dec 24, 2014 at 2:43 PM by jmcurl, version 1

Comments

No comments yet.