exmap permission errors

Bug #226626 reported by Charles Brunet
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
exmap (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Binary package hint: exmap

Installed exmap and exmap-modules-source, compiled module and installed it.
Hardy Heron, AMD64 version.

Errors when running: gksudo gexmap:
1 /lib/ld-2.7.so calc_maps_for_elf_file: can't calc map for seg
1 /lib/ld-2.7.so calc_maps_for_file: failed to calc elf file maps
calc_maps: failed to calc for /lib/ld-2.7.so
Failed to process maps for pid 1
Snapshot::load - failed to load: calculate file mappings
1: empty restriction to file [stack]
1: empty restriction to file /sbin/init
1: empty restriction to file [heap]
1: empty restriction to file [vsyscall]
1: empty restriction to file [anon]
1: empty restriction to file /lib/libc-2.7.so
1: empty restriction to file [vdso]
1: empty restriction to file /lib/ld-2.7.so
1: empty restriction to file [stack]
1: empty restriction to file /sbin/init
1: empty restriction to file [heap]
1: empty restriction to file [vsyscall]
1: empty restriction to file [anon]
1: empty restriction to file /lib/libc-2.7.so
1: empty restriction to file [vdso]
1: empty restriction to file /lib/ld-2.7.so
1: empty restriction to file [stack]
1: empty restriction to file /sbin/init
1: empty restriction to file [heap]
1: empty restriction to file [vsyscall]
1: empty restriction to file [anon]
1: empty restriction to file /lib/libc-2.7.so
1: empty restriction to file [vdso]
1: empty restriction to file /lib/ld-2.7.so
1: empty restriction to file /lib/ld-2.7.so
1: empty restriction to file /lib/libc-2.7.so
1: empty restriction to file /sbin/init
1: empty restriction to file [anon]
1: empty restriction to file [stack]
1: empty restriction to file /sbin/init
1: empty restriction to file [heap]
1: empty restriction to file [vsyscall]
1: empty restriction to file [anon]
1: empty restriction to file /lib/libc-2.7.so
1: empty restriction to file [vdso]
1: empty restriction to file /lib/ld-2.7.so

It then shows zero for all processes.

And when trying to run it as normal user:
Can't open file: /var/cache/nscd/passwd
File::load - can't open file: /var/cache/nscd/passwd
Can't open file: /var/cache/nscd/group
File::load - can't open file: /var/cache/nscd/group
Can't open file: /var/cache/nscd/services
File::load - can't open file: /var/cache/nscd/services
10963 /lib/ld-2.7.so calc_map_for_seg: non-file backed first vma
10963 /lib/ld-2.7.so calc_maps_for_elf_file: can't calc map for seg
10963 /lib/ld-2.7.so calc_maps_for_file: failed to calc elf file maps
calc_maps: failed to calc for /lib/ld-2.7.so
Failed to process maps for pid 10963
Snapshot::load - failed to load: calculate file mappings
Vma::get_pages_for_range - start pgnum out of range: 0, 0 [vsyscall]
sizes_for_mem_range: Can't get pages for range (ffffffffff600000,ffffffffff6010)
gexmap: /usr/include/boost/shared_ptr.hpp :315 : T* boost::shared_ptr<T>::opera.
Abandon

Charles Brunet (cbrunet)
description: updated
Revision history for this message
Rumpeltux (rumpeltux) wrote :

Did you try to sudo it?
I got a similar error:
$ gexmap
1857 /lib/ld-2.10.1.so calc_map_for_seg: non-file backed first vma
1857 /lib/ld-2.10.1.so calc_maps_for_elf_file: can't calc map for seg
1857 /lib/ld-2.10.1.so calc_maps_for_file: failed to calc elf file maps
calc_maps: failed to calc for /lib/ld-2.10.1.so
Failed to process maps for pid 1857
Snapshot::load - failed to load: calculate file mappings
Vma::get_pages_for_range - start pgnum out of range: 0, 0 [vsyscall]
sizes_for_mem_range: Can't get pages for range (ffffffffff600000,ffffffffff601000)
gexmap: /usr/include/boost/shared_ptr.hpp:419: T* boost::shared_ptr< <template-parameter-1-1> >::operator->() const [with T = Exmap::Sizes]: Assertion `px != 0' failed.
Aborted

Starting it with sudo however worked (in that sense that it started the gui).
Should yield an appropriate error-message though.

The bug is still valid because the GUI shows 0,0 for all values and I guess my system might be using slightly more RAM ;)

summary: - exmap not working
+ exmap permission errors
Revision history for this message
Thomas Hotz (thotz-deactivatedaccount) wrote :

Do you experience a apport crash report? Thank you!

Changed in exmap (Ubuntu):
status: New → Incomplete
Revision history for this message
Charles Brunet (cbrunet) wrote :

I no longer use this software, so can cannot tell if the bug still is relevant or not.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for exmap (Ubuntu) because there has been no activity for 60 days.]

Changed in exmap (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.