KERN EXEC on Socket Opening?

[nichojo]

My code is as follows:

void CConnection::ConnectL()
{

	iState = EConnecting;

	User::LeaveIfError( iSocket.Open( iSocketServer, KAfInet, KSockStream, KProtocolInetTcp ) );

	// Set port
	destAddr.SetFamily(KAfInet);
	destAddr.SetAddress(INET_ADDR(131,204,27,5)); 
	destAddr.SetPort(5000); 

	iSocket.Connect(destAddr,iStatus);	

	#ifdef __WINS__
    User::After( 1 );     // Fix to allow emulator client to connect to server
	#endif

	SetActive();
}

Debugging tells me that the:
User::LeaveIfError( iSocket.Open( iSocketServer, KAfInet, KSockStream, KProtocolInetTcp ) );

Throws a KERN-EXEC 3 error.

From this snippet, is there anything that jumps out at you guys that could be the cause?

Thanks!

[Jack Torrance]

Connected to socket sorver?

Jack

[nichojo]

Connected to socket sorver?

Jack

Sure enough, in my constructor I have this:

void CConnection::ConstructL()
{
User::LeaveIfError( iSocketServer.Connect() );
...

[wizard_hu_]

Can it happen that you also Close it?
Have you got multiple threads?
Which SDK do you use? If it is a 2nd edition SDK, does the issue happen in a GUI or a console-based project?

[nichojo]

Can it happen that you also Close it?
Have you got multiple threads?
Which SDK do you use? If it is a 2nd edition SDK, does the issue happen in a GUI or a console-based project?

Happens at both. I've modified the code now, here is the class in full:

http://dev.jodynichols.com/seniordes...Connection.cpp
http://dev.jodynichols.com/seniordes...e/Connection.h


If you wanted to look I would appreciate it immensely. Its not a lot of code so it probably won't take long to find the problem.

I now am getting a ESOCK Client Error 23. I don't see anything being closed though.

And this is the 3rd edition SDK and i've tried both a Console and GUI approach.

EDIT: Keep in mind this is barebones code. I will implement more functionality and control as I go, I just want to get this connection going to prove it works before I continue on.

[wizard_hu_]

Khm, in your actual code you use RConnection. Somehow you have forgot to mention this in previous posts. However you apparently Open and Start it.
Some minor suggestions could be
- the use of "const TDesC&" instead of "TBuf<256> &"
- iDestAddr instead of destAddr
May I ask how you instantiate and use CConnection?

[nichojo]

Khm, in your actual code you use RConnection. Somehow you have forgot to mention this in previous posts. However you apparently Open and Start it.
Some minor suggestions could be
- the use of "const TDesC&" instead of "TBuf<256> &"
- iDestAddr instead of destAddr
May I ask how you instantiate and use CConnection?

I added that RConnection a few hours ago as a test to see if that was I was missing.

In the console app main I use:


CConnection * iConnection;

and

TRAPD(connError, iConnection->ConnectL());
if (connError)
return connError;


Wizard, thank you so much for your help. I really appreciate it.

EDIT: This is for the console app.

[wizard_hu_]

CConnection * iConnection;

and

TRAPD(connError, iConnection->ConnectL());
if (connError)
return connError;

None of these lines show how you instantiate the class.

But OK, here is my version: if you instantiate the class with new(ELeave), but you forget invoking ConstructL, your initial iState would be EAuthenticating, thus the (iState == EDisconnected) block is skipped, so the very first occasion where anything bad can happen is the iSocket.Open. And actually the bad thing happens.

[david.caabeiro]

Beware of the control flow.. for instance, a quick look at your code shows a missing SetActive() after starting the RConnection, and of course the rest of the code relying on that RConnection should be called after RunL() is invoked. As a first test, I'd try to reduce the code instead of adding new things like the RConnection.

Make sure the async request is completed before issuing further requests..

Also, as wizard stated, beware of scope issues when using async functions (ie. avoid automatic vars)

[nichojo]

Beware of the control flow.. for instance, a quick look at your code shows a missing SetActive() after starting the RConnection, and of course the rest of the code relying on that RConnection should be called after RunL() is invoked. As a first test, I'd try to reduce the code instead of adding new things like the RConnection.

Make sure the async request is completed before issuing further requests..

Also, as wizard stated, beware of scope issues when using async functions (ie. avoid automatic vars)

Thanks! I've redone some things and I think things might be working. I will implement your instructions now.