Skip to content

Instantly share code, notes, and snippets.

🐢
learning

M4x bash-c

🐢
learning
Block or report user

Report or block bash-c

Hide content and notifications from this user.

Learn more about blocking users

Contact Support about this user’s behavior.

Learn more about reporting abuse

Report abuse
View GitHub Profile
View change-MAX_ORDER.patch
From 8611da05002c672526b7419ba125ea880d55b1f5 Mon Sep 17 00:00:00 2001
From: Mike Krinkin <krinkin.m.u@gmail.com>
Date: Sat, 13 Aug 2016 19:25:00 +0300
Subject: [PATCH] change MAX_ORDER constant to allow 1GB allocations
Signed-off-by: Mike Krinkin <krinkin.m.u@gmail.com>
---
arch/x86/include/asm/sparsemem.h | 6 +++---
include/linux/mmzone.h | 2 +-
2 files changed, 4 insertions(+), 4 deletions(-)
View logtrace.cpp
#include <fstream>
#include <cstring>
#include <string>
#include <cstdio>
#include <iostream>
#include "pin.H"
FILE *traceFile; // the file to store your trace
FILE *disFile; // the file to store your disassmbled_code
// ADDRINT imgHAddr; // the high address of loaded image
@bash-c
bash-c / memory_layout.md
Created Aug 14, 2018 — forked from CMCDragonkai/memory_layout.md
Linux: Understanding the Memory Layout of Linux Executables
View memory_layout.md

Understanding the Memory Layout of Linux Executables

Required tools for playing around with memory:

  • hexdump
  • objdump
  • readelf
  • xxd
  • gcore
You can’t perform that action at this time.