Python 1.4.5 -> 1.9.4 breaks bluetooth socket closing behaviour

[m_c_001]

Hi chaps,

We're looking to upgrade from 1.4.5 to 1.9.4 in order to benefit from some of the Python core 2.5.2 functionality, but in doing so some of the socket behaviour in our code has broken. Here are the relevant code snippets (apologies if the indentation formatting gets broken) .

We import the btsocket module as:

    import btsocket as socket

and instantiate a socket via:

  sock = socket.socket(socket.AF_BT, socket.SOCK_STREAM)

Data packets are then read via calls to the function:

  def receivePacket(sock):
    buffer = ""
    packetComplete = False

    while not packetComplete :
      try:
       ch = sock.recv(1)
      except:
        print "error communicating with sensor"
        continue

      # loop until packet received
      while(ch != '\n'):
        buffer += ch
        try:
          ch = sock.recv(1)
        except:
          print "error communicating with sensor"
          continue

      packetComplete = True

    return buffer

We also register a Disconnect function via the atexit module for when we terminate the application, which has the form:

  def Disconnect():
    global sock,

    # Close the Bluetooth socket
    sock.close()

    # other code removed

Now with 1.4.5 everything stops working cleanly when Disconnect is invoked, but with 1.9.4 the diagnostic string "error communicating with sensor" gets echoed (doesn't happen with 1.4.5) and the whole phone freezes up. Only rebooting the phone is then possible. Why does the thread of execution return to the receivePacket function in 1.9.4 when the function registered with atexit has been invoked? Is this a bug in 1.9.4?

Regards,
m

[ashwinurao]

... with 1.9.4 the diagnostic string "error communicating with sensor" gets echoed (doesn't happen with 1.4.5) and the whole phone freezes up. Only rebooting the phone is then possible. Why does the thread of execution return to the receivePacket function in 1.9.4 when the function registered with atexit has been invoked? Is this a bug in 1.9.4?

Regards,
m

Try to write the exception raised to a file and check the traceback. What does it say?

[m_c_001]

Changing the except clauses in receivePacket to print the exception message rather than the string in the original listing, i.e. the two clauses now read:

    except Exception, e:
      print "%s" % (e)

now displays the following prior to the phone freezing up:

(13, 'Permission denied')

Is this related to the problem described at the following link?

https://garage.maemo.org/tracker/ind...=854&atid=3201

m

[mahesh.sayibabu]

Is this related to the problem described at the following link?

https://garage.maemo.org/tracker/ind...=854&atid=3201

m

Looks like its the same bug, but if your observations are different from those mentioned in the bug tracker please update the tracker.

[m_c_001]

Looks like its the same bug, but if your observations are different from those mentioned in the bug tracker please update the tracker.

OK, report filed.