We have a local environment for testing our cloud WebRTC products. The media application runs locally on a MacBook along with a node.js server application. We connect using a web page which establishes connections. Our media application can be configured to use the localhost interface by default but also supports any non-localhost interface. On my MacBook (M1, macOS 14.3.1) I can no longer use the non-localhost interface. Wireshark captures show that STUN messages from the web application fail to get responded to on the non-localhost interface. Others who use a similar setup and the same software versions do not experience this issue. This used to work for me as well.
What are my options for debugging this issue?
Thanks,
Bob
Post
Replies
Boosts
Views
Activity
Need some help debugging an issue that only started after upgrading to Monterey. Our application is failing to start resulting in a segmentation fault. I am new to debugging such things on MacOS. Using lldb I get the following back trace. Tells me a little but I am unsure how to approach the issue. Looks like it may be related to loading symbols from a dynamic library? Oh, and yes, everything was rebuilt and all dependent libraries installed / upgraded with brew, etc.
Thanks,
Bob
(lldb) bt
* thread #1, stop reason = signal SIGSTOP
* frame #0: 0x0000000000000000
frame #1: 0x00007ff807e34bb2 libobjc.A.dylib`load_images + 1358
frame #2: 0x0000000115a0a41c dyld`dyld4::RuntimeState::notifyObjCInit(dyld4::Loader const*) + 170
frame #3: 0x0000000115a0fbfd dyld`dyld4::Loader::runInitializersBottomUp(dyld4::RuntimeState&, dyld3::Array<dyld4::Loader const*>&) const + 167
frame #4: 0x0000000115a0fbeb dyld`dyld4::Loader::runInitializersBottomUp(dyld4::RuntimeState&, dyld3::Array<dyld4::Loader const*>&) const + 149
frame #5: 0x0000000115a0fbeb dyld`dyld4::Loader::runInitializersBottomUp(dyld4::RuntimeState&, dyld3::Array<dyld4::Loader const*>&) const + 149
frame #6: 0x0000000115a0fcac dyld`dyld4::Loader::runInitializersBottomUpPlusUpwardLinks(dyld4::RuntimeState&) const + 108
frame #7: 0x0000000115a2332e dyld`dyld4::APIs::runAllInitializersForMain() + 222
frame #8: 0x0000000115a01358 dyld`dyld4::prepare(dyld4::APIs&, dyld3::MachOAnalyzer const*) + 3438
frame #9: 0x0000000115a004b4 dyld`start + 388