Confirmed users
523
edits
Mobile/Fennec/Debugging: Difference between revisions
Jump to navigation
Jump to search
no edit summary
(Created page with "Debugging Fennec can be trickier than Firefox because it uses multiple processes. For example to debug reftests in fennec on desktop linux the following recipe works: python ru...") |
No edit summary |
||
| Line 1: | Line 1: | ||
Debugging Fennec can be trickier than Firefox because it uses multiple processes. | Debugging Fennec can be trickier than Firefox because it uses multiple processes. | ||
For example to debug reftests in fennec on desktop linux the following recipe works: | For example to debug reftests in fennec on desktop linux the following recipe works: | ||
python runreftest.py --debugger=gdb TEST_PATH/reftest.list | python runreftest.py --debugger=gdb TEST_PATH/reftest.list | ||
once inside gdb | once inside gdb | ||
# this will break on | #this will break on fork calls | ||
(gdb) | (gdb) catch fork | ||
# | #this will break on exec calls | ||
(gdb) catch exec | |||
(gdb) | |||
# this will break on the exec | (gdb) run | ||
(gdb) break some_function_in_the content process | |||
#the first fork will be for glx probing and can be ignor | |||
(gdb) continue | |||
#the next fork is the content process, make sure we follow into it | |||
(gdb) set follow-fork-mode child (gdb) continue | |||
#this will break on the exec | |||
(gdb) break some_function_in_the content process | |||
<pre>sdqwd | |||
</pre> | |||