socket and threading ... bad file descriptor

Discussion in 'Python' started by hg, Sep 14, 2006.

  1. hg

    hg Guest

    Hi,

    I have two classes, one listens and accepts connections, gets the
    socket, reads the first byte from the opened socket then launches a
    thread (threading) and gives it the socket identifier.

    The first time the thread attempts to read from the given socket,
    socket.py raises a bad file descriptor in _dummy.

    I tried using plain threads with the same problem.

    Any clue ?

    Thanks,

    hg
    hg, Sep 14, 2006
    #1
    1. Advertising

  2. hg

    hg Guest

    hg wrote:
    > Hi,
    >
    > I have two classes, one listens and accepts connections, gets the
    > socket, reads the first byte from the opened socket then launches a
    > thread (threading) and gives it the socket identifier.
    >
    > The first time the thread attempts to read from the given socket,
    > socket.py raises a bad file descriptor in _dummy.
    >
    > I tried using plain threads with the same problem.
    >
    > Any clue ?
    >
    > Thanks,
    >
    > hg


    Bug discovered, sorry
    hg, Sep 14, 2006
    #2
    1. Advertising

Want to reply to this thread or ask your own question?

It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum.
Similar Threads
  1. Kevin
    Replies:
    4
    Views:
    1,043
    David Bolen
    Jul 7, 2003
  2. Replies:
    9
    Views:
    702
    Abhijit Soman
    Jan 6, 2005
  3. Vishnu
    Replies:
    0
    Views:
    499
    Vishnu
    Jan 6, 2005
  4. mbm

    [socket] test socket descriptor state

    mbm, Sep 27, 2007, in forum: C Programming
    Replies:
    2
    Views:
    422
    CBFalconer
    Sep 27, 2007
  5. rantingrick
    Replies:
    44
    Views:
    1,172
    Peter Pearson
    Jul 13, 2010
Loading...

Share This Page