Access violation when sending sth on closed port
Serial and TCP terminal for engineering and debugging
Brought to you by:
crun
Menu
▾
▴
#85 Access violation when sending sth on closed port
While the port is closed (so this describes admittedly not a useful user scenario), an access violation is thrown when something is being sent via the "Send" tab in one of the the input lines (enter content, click on either "Number", "as Hex" or "as ASCII", then the violation occours).
[Window Title]
Information
[Content]
Last Error Message was:
Error in SendString,
Access violation at address 779DFF33 in module 'ntdll.dll'. Write of address 000000E0
RealTerm: Serial Capture Program 3.0.0.33
C:\Program Files (x86)\BEL\Realterm\realterm.exe 25.06.2017
CodeSigned by Broadcast Equipment Ltd
Windows (Version 6.2, Build 9200, 64-bit Edition)
Memory Used: 1899kb Run 7 times 22,8 hrs
ctrl-C to copy this to clipboard
[OK]
Seem to be two issues:
a) Not-autoopening first time i.e when port has not been open before
b) showing error message / error message obscure.
In case B, what do you expect RT to do when the user send to a closed or non-existent port?
(when auto-open is not set)
Disabling the send functionality would be the most user friendly solution (maybe with a status string "port closed" withing the send data area) as it gives the user feedback even before s/he performs a useless action.
fixed in 3.1.34
no longer brings up error dialog
auto-open is acting properly first time
The icon shows X when port is closed, and error light and error message in status bar will show.
Because a vaild port will auto-open, it is not so useful to know it is not open.
I can confirm this is fixed in 3.0.1.44.