Closed
Bug 891108
Opened 13 years ago
Closed 13 years ago
Get valgrind working on B2G Jelly Bean
Categories
(Firefox OS Graveyard :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: qdot, Assigned: qdot)
References
Details
(Keywords: perf, Whiteboard: [c=profiling s=2013.08.09])
There are a few problems with running valgrind on B2G with a 4.2.2 kernel:
- Small build errors in the valgrind tree due to some structs that don't exist in < 4.2.2 that now do
- Need to add valgrind to the 4.2.2 manifests
- Haven't gotten valgrind to successfully run yet, possibly due to library differences?
Since we're quickly approaching having releases built on top of this kernel, as well as having platforms with FAR more resources (multiple cores and 2gb of RAM on the n4!), it'd be nice to get all of this cleaned up and going.
| Assignee | ||
Comment 1•13 years ago
|
||
Valgrind now at least runs successfully, but spawning child processes (which we never even got to on unagi before smacking into OOM issues) crashes because of issues with libxul locations and linking.
| Assignee | ||
Comment 2•13 years ago
|
||
All fixed, but since 4.3 is now the /only/ platform we work on due to the nexus 4 being the only platform with enough resources to run valgrind, there's no specific code changes. Marking resolved.
Assignee: nobody → kyle
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•