search

g4klx / MMDVMHost

The host program for the MMDVM
GNU General Public License v2.0
378 stars 274 forks source link

MMDVMHost: UDPSocket...error #793

Closed labdvm closed 9 months ago

labdvm commented 9 months ago

Hi, just recompiled latest MMDVMHost and I get this error: MMDVMHost: UDPSocket.cpp:224: int CUDPSocket::read(unsigned char*, unsigned int, sockaddr_storage&, unsigned int&): Assertion `m_fd >= 0' failed.

What should I do ? 73, Z32IT

overnite commented 9 months ago

I have the exact same issue

labdvm commented 9 months ago

I have the exact same issue

I have recompiled one backward version and works ok.

g4klx commented 9 months ago

Maybe providing a copy of your log file and/or your configuration file would be a good start. On Wednesday, 31 January 2024 at 20:59:22 GMT, labdvm @.***> wrote:

Hi, just recompiled latest MMDVMHost and I get this error: MMDVMHost: UDPSocket.cpp:224: int CUDPSocket::read(unsigned char*, unsigned int, sockaddr_storage&, unsigned int&): Assertion `m_fd >= 0' failed.

What should I do ? 73, Z32IT

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you are subscribed to this thread.Message ID: @.***>

g4klx commented 9 months ago

In the absence of any logs or a configuration file, I have looked around the source code and made some changes which may help. If you build from the latest sources, which are dates 20240201 and see if that helps. I was unable to reproduce it here with my system.

labdvm commented 9 months ago

In the absence of any logs or a configuration file, I have looked around the source code and made some changes which may help. If you build from the latest sources, which are dates 20240201 and see if that helps. I was unable to reproduce it here with my system.

OK, I will recompile today version.

labdvm commented 9 months ago

OK, 20240201 works !

overnite commented 9 months ago

Excellent, just did it and now have it workingThanksBryanSent from my iPhoneOn Feb 1, 2024, at 2:37 PM, Jonathan Naylor @.***> wrote: In the absence of any logs or a configuration file, I have looked around the source code and made some changes which may help. If you build from the latest sources, which are dates 20240201 and see if that helps. I was unable to reproduce it here with my system.

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you commented.Message ID: @.***>