On 11/23/2015 7:58 AM, Alexander Abagian wrote:
Visual Studio (2013) debugger doesn't stop at breakpoints placed in some modules like
WebRTC and nICEr. As I googled, the reason of this depends on the fact that xul.dll,
contained these modules, "did not load at the default load address" (as it's
hinted in the module list).
Could somebody help me with build configuration flags to force xul.dll be
loaded at the default address or to build it as a static lib ? Or any other way
to make the breakpoints stoppable.
Needed pdb is loaded.
I normally debug locally-built copies (there are instructions on
developer.mozilla.com about how to set up symbol-pulling, which it seems
you have done).
One possibility - if you're using e10s (multi-process isolation, the
default in local builds of m-c, Nightly, or Developer Edition), then you
need to debug the Web Content process (which is typically running
plugin-container). WebRTC code runs there, and uses IPC to the master
process to do network IO/etc.
You can turn off e10s in preferences and restart the browser as well.
--
Randell Jesup, Mozilla
_______________________________________________
dev-media mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-media
