pDebug | Programmable NodeJS Debugger | Runtime Evironment library

I have changed a couple of things to this script in order to get it working.

1. It seems that forward slashes are using as well. So you can just do "text": "upload THIS/FOLDER/STRUCTURE/IS/WORKING /SOMEWHERE/ON/QNX
2. ${workspaceRoot} still wasn't working, but I used VS Code Power Tools to make some custom commands that can be added to your build script and you can simply call them via ${command:myCustomCommand}. Inside of those commands, you can also call other commands, like cmake.launchTargetPath and change it to forward slashes with simple javascript regex.

To answer your question: no, memory will not be leaked. Whenever object A goes out of scope, the destructor will be called, where destructor for CDebug will be called and memory freed.

But as I am very happy when people want to learn how to use unique_ptr, I wanted to point out two things with the code.

Firstly, the nullptr check in the constructor for A is redundant.

Once the kernel is running, should it recognize, automatically, and update the data in the file /proc/interrupt?

Yes it will update, once the interrupt is registered.

Value returned by the kernel's .write function is interpreted as:

• error code, if it is less than zero (<0),

• number of bytes written, if it is more than or equal to zero (>=0)

So, for tell user that all bytes has been written, .write function should return its count parameter.

In case of .write function, returning zero has a little sense: every "standard" utility like echo will just call write() function again.

There is no way one can debug qnx apps with Ubuntu's gdb.

You have to use qnx's gdb built for the exact this purpose, that is able to run target qnx and many other commands you will need. You have to use qnx's gdb on your host and pdebug on your target and run the same commands you ran: