I hereby claim:
- I am cojocar on github.
- I am cojocar (https://keybase.io/cojocar) on keybase.
- I have a public key whose fingerprint is 1DA3 C639 B10C 215A 62ED 43ED 019E 4BA4 F235 22D6
To claim this, I am signing this object:
I hereby claim:
To claim this, I am signing this object:
$ git clone git://repo.or.cz/tomato.git
$ cd tomato
$ git checkout tomato-shibby-RT-AC
$ sudo ln -s full/path/to/tomato/tools/brcm /opt
$ export PATH=${PATH}:/opt/brcm/hndtools-mipsel-linux/bin:/opt/brcm/hndtools-mipsel-uclibc/bin:/mnt/a/projects/tomato/release/tools
$ git describe --tags
ShibbyRT-N_095-624-ga45b4d6
$ find /bin /usr/bin/ /sbin/ -executable -exec ldd {} \; 2>/dev/null | cut -f1 -d' ' | tr -d '\t' | grep -ve "^not$" | sort | uniq -c | sort -n -k1 -r > /tmp/all-find
$ head -100 /tmp/all-find
2969 libc.so.6
2968 linux-vdso.so.1
2968 /lib64/ld-linux-x86-64.so.2
1528 libdl.so.2
1514 libm.so.6
1444 libpthread.so.0
1141 libz.so.1
For x86, because we don't have any "special" symbols, the output is the same for strip vs nostrip. ".word 0x9090" which is data is interpreted as code because of the linear disassambly behavior. The special symbols are documented here: https://sourceware.org/binutils/docs-2.23/as/ARM-Mapping-Symbols.html
For ARM objdump (and the tools alike), because symbols are used to determine if we have code ore data the linear disass knows where is data and where is code.
#!/usr/bin/env python | |
import matplotlib.pyplot as plt | |
import matplotlib.patches as patches | |
COLORS = plt.style.library['bmh']['axes.color_cycle'] | |
def show_colors(): | |
fig, ax = plt.subplots(1) |