Android Question Finding The Error Line Number in Code

[aaronk]

Hi,

I have a error when trying to connect using SSL using Android L. (works fine on all other versions of Android except Android L)

I have reported this to the Android Developer Preview issues site, and now they are asking me to provide the line number the error occurs.

I am not sure how to get this line number.

https://code.google.com/p/android-developer-preview/issues/detail?id=1058

The error that is shows in the B4A IDE Log is:

javax.net.ssl.SSLHandshakeException: SSL handshake terminated: ssl=0xb80c63f0: SSL_ERROR_ZERO_RETURN occurred. You should never see this.
 at com.android.org.conscrypt.NativeCrypto.SSL_do_handshake(Native Method)
 at com.android.org.conscrypt.OpenSSLSocketImpl.startHandshake(OpenSSLSocketImpl.java:320)
 at com.maximussoft.socketssl.SocketSSL$2.run(SocketSSL.java:109)
 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:422)
 at java.util.concurrent.FutureTask.run(FutureTask.java:237)
 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
 at java.lang.Thread.run(Thread.java:818)

The code I am running is attached.

I tried looking at the line numbers it shows above, but can't work out exactly what one I should be telling them, or even where the error is in the Java Code.

Anyone able to help me provide the correct information so that I can pass it on to Google ?

 

[Erel]

It happens in line 320 of the class com.android.org.conscrypt.OpenSSLSocketImpl.

 

[aaronk]

It happens in line 320 of the class com.android.org.conscrypt.OpenSSLSocketImpl.

If this is not a silly question where about is that class kept ?
I can't seem to find that section in any of the java files.

I am guessing that Google will come back saying that they can't see that part of the code.

 

[Erel]

It is part of Android OS.

 

[KMatle]

"You should never see this" Wait for an update.

 

[aaronk]

I have posted the reply to Google, and now just need to wait for there reply.
Fingers crossed they find and fix the bug.