Firefox/Tegra/Device Debugging: Difference between revisions

No edit summary
Line 51: Line 51:
## After rechecking the above settings (sometimes the UI will lose your changes!), click "Close"
## After rechecking the above settings (sometimes the UI will lose your changes!), click "Close"
# From the menubar, select Target --> Attach Device. If prompted for an image, select NK.NB0 from the OS image dir you used when reflashing the device.
# From the menubar, select Target --> Attach Device. If prompted for an image, select NK.NB0 from the OS image dir you used when reflashing the device.
# The device will finish booting, and you will see some bootup spam in the Output tab of VS. You may see a popup window for "Download Runtime Image" stuck at "Waiting for BOOTME from CE device" -- this is ok.
# XXX I get a prompt asking to locate "nk.exe". Just click cancel?
# XXX For the debugger to find symbols for apps, Debug -> Symbol Search Path; put the bin dir, e.g. C:\proj\firefox-wince\dist\bin in there
# The device will finish booting, and you will see some bootup spam in the Output tab of VS. You may see a popup window for "Download Runtime Image", ignore it.
# From the menubar, select Debug -> Symbol Search Path. Enter the full path to your dist/bin dir. EG: <code>C:\proj\firefox-wince\dist\bin</code>


= Using the debugger =
= Using the debugger =


XXX Setting breakpoints sometimes requires you to look up the symbol's address using the watch window, and then to set a breakpoint in the disassembly view.  Use MSVC context specifiers to specify the dll, e.g.:  {,,xul.dll}SomeFunction  to specify "SomeFunction" inside xul.dll (note two commas).
XXX Setting breakpoints sometimes requires you to look up the symbol's address using the watch window, and then to set a breakpoint in the disassembly view.  Use MSVC context specifiers to specify the dll, e.g.:  {,,xul.dll}SomeFunction  to specify "SomeFunction" inside xul.dll (note two commas).
canmove, Confirmed users
432

edits