Closed Bug 916627 Opened 11 years ago Closed 11 years ago

/proc/$PID/maps have length 0

Categories

(Firefox OS Graveyard :: General, defect)

Product:
Firefox OS Graveyard
Component:
General
Platform:
ARM
Gonk (Firefox OS)
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED INVALID

People

(Reporter: bjacob, Unassigned)

References

Details

I don't seem to have access of process memory mappings in the /proc/$PID/maps files anymore, on hamachi / B2G master branch. The /proc/$PID/maps files exist, but they have length 0. Having them would be nice to understand e.g. bug 916626.
What are the permissions on /proc/PID/maps? And what user were you running as when trying to access the files?
(In reply to Dave Hylands [:dhylands] from comment #1) > What are the permissions on /proc/PID/maps? Oh... the permissions are 0600. I see. > > And what user were you running as when trying to access the files? ...I was the default user for adb shell. With 'su', it works. And of course, the 'length 0' is normal for such a special file. It's just that this command, $ adb shell cat /proc/144/maps /proc/144/maps: invalid length gave me that confusing error message. sorry about the noise, and thanks.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → INVALID
(In reply to Benoit Jacob [:bjacob] from comment #2) > (In reply to Dave Hylands [:dhylands] from comment #1) > > And what user were you running as when trying to access the files? > > ...I was the default user for adb shell. So, depending on the phone, you could be using a root user (which has # in the prompt) or a shell user (which has $ in the prompt). The root user can look into the 0600 file, while the shell user can't. > With 'su', it works. This suggests that you had a shell user. On some phones, you can use the command "adb root" to relaunch adbd on the phone as the root user, which in turn gives the root user when you use adb shell. On rooted production phones, you have to use su to get root. On non-rooted production phones, su won't work either.
Yes, I had a shell ($) user. Thanks for the explanation, I didn't know about adb root.
You need to log in before you can comment on or make changes to this bug.