Introduce erl_drv_command_error()

[rickard-green]

• int erl_drv_command_error(ErlDrvPort port, char *error_reason)

  Generate an error exception, with the reason error_reason as an atom, in a call to the erlang:port_command/2 BIF or the erlang:port_command/3 BIF. The error can only be generated from the drivers outputv() or output() callbacks, which implements port command, when the port command has been initiated via one of the synchronous port_command() BIFs. When the port command has been initiated by the asynchronous Port ! {Owner, {command, Data}} construct, this call will fail and no exception will be generated.

  error_reason needs to be a null terminated latin1 string. If the string is longer than 255 characters (excluding the null termination character), it will be truncated to 255 characters.

  Returns zero on success and a non-zero integer on failure.

[github-actions]

CT Test Results

       3 files     125 suites   42m 43s ⏱️
1 503 tests 1 452 ✔️ 51 💤 0 ❌
1 815 runs  1 746 ✔️ 69 💤 0 ❌

Results for commit 68bad4d.

♻️ This comment has been updated with latest results.

To speed up review, make sure that you have read Contributing to Erlang/OTP and that all checks pass.

See the TESTING and DEVELOPMENT HowTo guides for details about how to run test locally.

Artifacts

• Complete CT logs (Download Logs)
• HTML Documentation (Download HTML Docs)
• Windows Installer

// Erlang/OTP Github Action Bot

[rickard-green]

@RaimoNiskanen for use when solving #6455

[sverker]

What about changing argument char* error_reason to ErlDrvTermData error_reason_atom to be created by existing driver_mk_atom(). Two advantages:

• Avoid introducing Latin1 string in new API.
• Can be used more efficient by calling driver_mk_atom() once at driver load time.

[rickard-green]

@RaimoNiskanen Closing this since it cannot be used in solving #6455. Looking into other alternatives...