Closed Bug 969051 Opened 11 years ago Closed 10 years ago

get_about_memory.py could automatically retrieve build settings from .userconfig

Categories

(Firefox OS Graveyard :: GonkIntegration, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: bkelly, Assigned: erahm)

References

Details

Attachments

(1 file)

The get_about_memory.py script needs to know where the gecko object directory is to do things like fixup symbols in DMD reports. Right now the user has to know to pass this information in with the --gecko-objdir argument. We could make this a little bit easier if we had get_about_memory.py launch a shell process to read .userconfig and print out the resulting value of the $GECKO_OBJDIR. The python code could then use that value to find the symbols.
This would also be useful for |--product|. I'm guessing we can do whatever |mach| does to work this stuff out, or if we're linux/mac only it should be pretty straightforward. A super simple POC bash script: #!/bin/bash . load-config.sh python tools/get_about_memory.py --gecko-objdir "${GECKO_OBJDIR}" "$@"
This patch attempts to deduce the --gecko-objdir and --product params used when processing DMD logs.
Attachment #8479461 - Flags: review?(jld)
Assignee: nobody → erahm
Status: NEW → ASSIGNED
Attachment #8479461 - Flags: review?(jld) → review+
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: