-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 How can I tell trinity to not mremap it ? On 03/01/2014 10:34 AM, Richard Weinberger wrote: > On Sat, Mar 1, 2014 at 10:28 AM, Toralf Förster > <toralf.foerster@xxxxxx> wrote: >>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 >>> >>> Today I tested if I can activate that syscall again here >>> (munmap works fine since few days). Testing a 32 bit user mode >>> linux image with "$>trinity -q -N 100000 -C 8" gave in the >>> syslog of the UML guest: >>> >>> Mar 1 10:09:18 trinity kernel: Stub registers - Mar 1 >>> 10:09:18 trinity kernel: 0 - 100000 > Looks like the stub page. You cannot remap it. If you do so the > calling process will die. > - -- MfG/Sincerely Toralf Förster pgp finger print:1A37 6F99 4A9D 026F 13E2 4DCF C4EA CDDE 0076 E94E -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iF4EAREIAAYFAlMTHgIACgkQxOrN3gB26U7mJAD+NoKRpLbpLjbQyry7y0Ngkbmx oH9pVUr0bu1tbbfB+pYBAIQ+scnrW97kngcFAM2bJb/R9fp6osEB4AbPpV5ZEmwC =hgfr -----END PGP SIGNATURE----- -- To unsubscribe from this list: send the line "unsubscribe trinity" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
