Closed czyba closed 7 years ago
I was able to reproduce this issue as well in another situation:
Hi @czyba , thanks for reporting this issue. Let me compare with our connection tests and verify if I get a repro. Good that you attached the callstack already, really appreciated.
Hi @czyba, a fix was just checked in for this sample, please verify if you have a chance and let us know. Thanks, Azure IoT Team.
Hi @ewertons,
it works on my end. Thanks.
Hi Azure SDK Team,
I ran into a segfault in the following situation on Debian Jessie and Gentoo Linux. I tested with the current master ( df786d7b1fd167640bb61f0deb9bcc62109ee74b ) and release_2017_07_14. This issue seems similar to the issues #167 and #160, the cause, however, at least from what I can tell from my gdb sessions and traces, seems to be different.
You can reproduce the issue by executing the following steps:
Note: Disconnecting before starting the program is the key here. If you start the program, wait until the connection to the iothub is established, disconnect from the internet, reconnect again, and wait for a couple of minutes, it will send the remaining enqueued messages just fine.
I was able to reproduce this consistently on both machines. Here is the gdb trace from my gentoo machine. At the bottom you can see the actual line that triggers the segfault and the reason from my print messages:
I hope this helps. Kind regards Christopher Czyba