The Valgrind Test Job
the valgrind test job builds the browser and runs it under valgrind, which can detect various common memory-related errors.
... the valgrind test job builds the browser and runs it under valgrind, which can detect various common memory-related errors.
... the valgrind test job builds the browser and runs it under valgrind, which can detect various common memory-related errors.
...And 11 more matches

Hacking Tips
n <path>, set dot-bin <path>, set pngviewer-bin <path>) within gdb.
...thin gdb.
...s shell executable that shares a directory with a file name "js-gdb.py".
...And 6 more matches

Performance
ing refcount tracing and balancing are ways to track down leaks caused by incorrect uses of reference counting.
...unt tracing and balancing are ways to track down leaks caused by incorrect uses of reference counting.
...counting.
...And 3 more matches

Testing Mozilla code
nightly project involves building a firefox nightly browser with the popular addresssanitizer tool and enhancing it with remote crash reporting capabilities for any errors detected.clang static analysisthis document is split in two parts.
...efox nightly browser with the popular addresssanitizer tool and enhancing it with remote crash reporting capabilities for any errors detected.clang static analysisthis document is split in two parts.
...coverage essentially is about measuring how often certain lines are hit, branches taken or conditions met in a program, given some test that you run on it.
...And 3 more matches

Continuous Integration
mpilation and some compiled-code tests (e.g., 'make check').
...ake check').
...builds; user builds are denoted with b, the same as for desktop and android builds.

Leak-hunting strategies and tips
pcwrappedjs is a sign that there could be significant numbers of js objects leaked.) for example, start with bringing up the mail window and closing the window without doing anything.
...ount_{ctor,dtor} all tier 1 platforms debug build (or build opt with --enable-logrefcnt) leaksoup (part of tracemalloc) all objects?
... opt with --enable-logrefcnt) leaksoup (part of tracemalloc) all objects?

Debugging
lldb is the new debugger on mac.
...the new debugger on mac.

SpiderMonkey 1.8.5
can treat as potential gc roots.
..._enterlocalrootscope api, and in many cases the need to explicitly root gc things or use the "root as you go" approach popular with earlier spidermonkey releases.

SpiderMonkey 1.8.7
can treat as potential gc roots.
..._enterlocalrootscope api, and in many cases the need to explicitly root gc things or use the "root as you go" approach popular with earlier spidermonkey releases.

Secure Development Guidelines
int argc, char *argv[]) { if (argc > 1) printf(argv[1]); } format string bugs: prevention easy to fix: always use a format string specifier: int main(int argc, char *argv[]) { if (argc > 1) printf("%s", argv[1]); } double free example: void* ptr = malloc(1024); if (error) { free(ptr); } free(ptr); double free: prevention set a pointer to null when it’s freed valgrind or malloc debugging can help detect those bugs use after free accessing data after a free() or delete can lead to undefined behavior some debug tools might be able catch some cases un-initialized data example: int main() { char *uninitialized_ptr; printf("0x%08x\r\n", uninitialized_ptr); return 0; } $ ./test 0x8fe0103 un-initialized data: prevention initialize y...
...cases un-initialized data example: int main() { char *uninitialized_ptr; printf("0x%08x\r\n", uninitialized_ptr); return 0; } $ ./test 0x8fe0103 un-initialized data: prevention initialize your variables!

NSS_3.12_release_notes.html
or_with_h1 allocates and leaks sha1cx bug 341122: coverity 633 sftk_destroyslotdata uses slot->slotlock then checks it for null bug 351140: coverity 995, potential crash in ecgroup_fromnameandhex bug 362278: lib/util includes header files from other nss directories bug 228190: remove unnecessary nss_enable_ecc defines from manifest.mn bug 412906: remove sha.c and sha.h from lib/freebl bug 353543: valgrind uninitialized memory read in nsspkiobjectcollection_addinstances bug 377548: nss qa test program certutil's default dsa prime is only 512 bits bug 333405: item cleanup is unused deadcode in secitem_allocitem loser bug 288730: compiler warnings in certutil bug 337251: warning: /* within comment bug 362967: export secmod_deletemoduleex bug 389248: nss build failure when nss_enable_ecc is not define...

Running Automated JavaScript Tests
e-level functionality, you may wish to use jstests.py path_to_js_shell --exclude=test262 other options allow you to show the test command lines being run, command output and return codes, run tests named in a given file, exclude tests named in a given file, hide the progress bar, change the timeout, run skipped tests, print output in tinderbox format, run a test in the debugger, or run tests in valgrind.

Exploitable crashes
ough normal testing and usage, when developers recognize a crash stack in gdb or submitted to a bug as exploitable.