The normal way to handle this is either to store the IP address in a file
I thought about it but how would you make cb aware of this file? Using a script?By patching C::B of course and fixing the real problem.
Isn't there any way to specify the remote ip as a global IDE settings?Why don't you use a macro / global compiler variable / environment variable for that purpose? All three solutions should work and are not saved inside the project file.
I thought about it but how would you make cb aware of this file?
Why don't you use a macro / global compiler variable / environment variable for that purpose? All three solutions should work and are not saved inside the project file.
Why would CB need to be aware of it? It's your code that needs to know about it.
QuoteWhy don't you use a macro / global compiler variable / environment variable for that purpose? All three solutions should work and are not saved inside the project file.
I tried to use a global compiler variable but cb didn't detect it (I'm using a lot of other global compiler variables in the project without any problems). I will have to investigate it a little further tomorrow morning.
What you haven't stated, which is perhaps what some of the replies have missed, is whether you are setting the IP in "Project->Properties->Debugger".
There may be a workaround or a simple fix we can make, but I'm not all that familiar with that part of the code base, so don't have immediate suggestions.
Ah - I missed that, to.QuoteWhat you haven't stated, which is perhaps what some of the replies have missed, is whether you are setting the IP in "Project->Properties->Debugger".Yes that's exactly what I do. I should have said that, my bad.
class GdbCmd_RemoteTarget : public DebuggerCmd case RemoteDebugging::TCP:
{
if (!rd->ip.IsEmpty() && !rd->ipPort.IsEmpty())
m_Cmd << targetRemote << _T("tcp:") << rd->ip << _T(":") << rd->ipPort;
}
It should be a 1-3 liner actually... I wonder what oBFusCATed has to tell...Well here it is: a two-liner. :-)
But please separate the patch. One patch for the formatting and one to fix the problem. Pretty please.Oh dear... this just came from the fact that there was one additional line where I indented an if-statement. Isn't your request a little over-done therefore? Notice that the #includes had to change, so this is part of the patch to work.
generally playing with the RunQueue is not pretty safe.That was my feeling, too. So I'd rather keep the patch as it is.