Re: crash while cancelling an in-progress connection

2014-11-21 Thread Hannu Mallat

On 20.11.2014 23:12, Thomas Green wrote:

issue is that when I attempt this, that after I make the dbus call to
disconnect, and before the disconnect call returns I get a
segmentation fault.  The stack is hammered enough that the only
traceback information is that it happens in libdbus-1.so.3.  This
only happens when I try to cancel a connection on an open AP.
Cancelling all other attempts have worked to this point.  Is there
something that I need to set a guard around so this doesn't happen?


Could you compile connman with debugging enabled and optimization 
disabled, and debug the issue with valgrind? Once the issue is 
reproducible that will help a lot in understanding what goes wrong.


BR,
H.
___
connman mailing list
connman@connman.net
https://lists.connman.net/mailman/listinfo/connman


crash while cancelling an in-progress connection

2014-11-20 Thread Thomas Green
I have a situation where the user has sent a connection to an open AP.  Before 
connman returns that the connection has completed, the user attempts to cancel 
the connection.  According to the documentation the 
net.connman.Service.Disconnect can also be used to abort a previous connection 
attempt via the Connect method.  The issue is that when I attempt this, that 
after I make the dbus call to disconnect, and before the disconnect call 
returns I get a segmentation fault.  The stack is hammered enough that the only 
traceback information is that it happens in libdbus-1.so.3.  This only happens 
when I try to cancel a connection on an open AP.  Cancelling all other attempts 
have worked to this point.  Is there something that I need to set a guard 
around so this doesn't happen?

Thanks 

Tom
___
connman mailing list
connman@connman.net
https://lists.connman.net/mailman/listinfo/connman


Re: crash while cancelling an in-progress connection

2014-11-20 Thread Tomasz Bursztyka

Hi,


I have a situation where the user has sent a connection to an open AP.  Before connman 
returns that the connection has completed, the user attempts to cancel the connection.  
According to the documentation the net.connman.Service.Disconnect can also be used 
to abort a previous connection attempt via the Connect method.  The issue is that 
when I attempt this, that after I make the dbus call to disconnect, and before the 
disconnect call returns I get a segmentation fault.  The stack is hammered enough that 
the only traceback information is that it happens in libdbus-1.so.3.  This only happens 
when I try to cancel a connection on an open AP.  Cancelling all other attempts have 
worked to this point.  Is there something that I need to set a guard around so this 
doesn't happen?


What version of connman and wpa_supplicant are you using?

Also, please provide any relevant logs you could have (the backtrace and 
so on).

Try running connman this way:
CONNMAN_SUPPLICANT_DEBUG=1 connmand -n -d  connman_log.txt

and paste the logs somewhere.

Thanks,

Tomasz
___
connman mailing list
connman@connman.net
https://lists.connman.net/mailman/listinfo/connman