CGsTypeBase** m_Members = new CGsTypeBase*[m_MemberCount]; // Is this the correct way to create an array of pointers?
As others have pointed out the your solution works because of the way the memory lays down.
In the above you have a declaration of a variable which has a type. And you also give the variable a value. But the declaration of the variable is a pointer. Just a pointer. Not a pointer to an array. So when intellisense sees you use it as an array it goes basically 'pointer + 1' isn't going to work. It does works because of the value and not the declaration.
I believe there is a declaration form that allows you to specify the form that would make intellisense happy but been a long time since I attempted C++ so I will leave it to someone else to come up with the form that makes the array specific.
Services run, by default, under the LocalService account, which is an extremely limited account. You can set your service to run as one of the predefined LocalService, NetworkService, or LocalSystem accounts, OR you can create your own account, assign privileges to it, and run your service under that account.
Note that use of LocalSystem is not recommended, as it essentially gives your service access to anything on the platform!
If you are running a debugger under a service, you may wish to allow the service to interact with the user.
I just tried getting the address in the debug window but could not find any way to do it. But if you add a call to GetLastError and set a breakpoint at that address, the debugger will stop at the call. I am not sure what you would gain by it even if you could find the address, since you cannot step into most Window functions.
I am not sure what you would gain by it even if you could find the address
I must debug an executable for which I do not have the source, and I need to determine which Winsock mode it's using, overlapped I/O, completion ports, select event, etc. I figured I would do this by placing breakpoints at all of the various Winsock functions and examining the arguments being passed.
The difficult we do right away...
...the impossible takes slightly longer.
Without the source you will not be able to see very much. The debugger only works with the debug information created by the compiler and linker, and built into the PDB file. Without that and the source files you will most likely not be able to find anything.
Since we have no idea what you installed it is difficult to give an answer. You should check the output from the install to see what happened. You can also use the list sub-command to check what has been installed.
Last Visit: 31-Dec-99 18:00 Last Update: 1-Oct-23 11:03