[Galaxy Note II Q&A, Help & Troubleshooting] debuggerdman:
debuggerd.exynosabuse

From what I can see, the /system/bin/debugger has been replaced with a script that reads:

#!/system/bin/sh

chmod 0400 /dev/exynos-mem

/system/bin/debuggerd.exynosabuse

Then, debuggerd.exynosabuse seems to launch instead of the normal debuggerd. I suppose some applications may call debuggerd by design, which explains why there are some random popups. Here are the "strings" for debuggerd.exynosabuse which appears to be the renamed original (need to verify). This thread then shows that it appears to do the reported actions.. by design? Would be interesting to trace it down a bit more to determine if the carrier/app developer is sending process dumps back to home for analysis which could contain sensitive data.

ELF

p\4

/system/bin/linker

__aeabi_unwind_cpp_pr0

__dso_handle

__INIT_ARRAY__

__FINI_ARRAY__

memset

property_get

atoi

__stack_chk_fail

__stack_chk_guard

__android_log_vprint

open

close

__errno

strcmp

strlen

vsnprintf

__aeabi_unwind_cpp_pr1

snprintf

strcpy

fprintf

__sF

calloc

free

strdup

fputs

strftime

write

strerror

strtoul

_edata

__bss_start

_end

realloc

memmove

read

socket_local_client

socket_local_server

getsockopt

fopen

fgets

fclose

fcntl

poll

accept

usleep

ioctl

dump_tombstone

dump_backtrace_to_file

getpid

__isthreaded

memcmp

sprintf

__libc_init

fchown

chown

stat

mkdir

sigaction

inotify_init

inotify_add_watch

kill

ptrace

opendir

readdir

readdir_r

closedir

fileno

waitpid

bsd_signal

time

system

fflush

localtime_r

unwind_backtrace_ptrace

demangle_symbol_name

get_backtrace_symbols_ptrace

find_symbol_ptrace

free_backtrace_symbols

format_backtrace_line

try_get_word_ptrace

load_ptrace_context

free_ptrace_context

liblog.so

libcutils.so

libc.so

libcorkscrew.so

/proc/%d/cmdline

%F %T

----- pid %d at %s -----

Cmd line: %s

<unknown>

/proc/%d/comm

"%s" sysTid=%d

Could not attach to thread: %s

Could not obtain stack trace for thread.

%s

ptrace detach from %d failed: %s

/proc/%d/task

----- end %d -----

Sending request to dump task %d.

Error dumping backtrace.

Error dumping tombstone.

Tombstone written to: %s

cannot get credentials

timed out reading tid

read failure? %s

invalid crash request of size %d

/proc/%d/task/%d

tid %d does not exist in pid %d. ignoring debug request

/proc/%d/status

Tgid:

Uid:

Gid:

tid %d does not exist. ignoring explicit dump request

ptrace attach failed: %s

debug.db.uid

failed responding to client: %s

ptrace continue failed: %s

dumpstate -k -t -z -d -o /data/log/dumpstate_app_native -m %d

!@%s

process stopped due to unexpected signal %d

********************************************************

* Process %d has been suspended while crashing. To

* attach gdbserver for a gdb connection on port 5039

* and start gdbclient:

* gdbclient app_process :5039 %d

* Wait for gdb to start, then press HOME or VOLUME DOWN key

* to let the process continue crashing.

********************************************************

/sys/class/leds/red/brightness

/sys/class/leds/green/brightness

/sys/class/leds/blue/brightness

/sys/class/leds/red/device/blink

/sys/class/leds/left/cadence

0,0

255

1,0

debuggerd resuming process %d

debuggerd committing suicide to free the zombie!

logd

android:debuggerd

debuggerd: Oct 4 2012 16:24:21

Usage: -b [<tid>]

-b dump backtrace to console, otherwise dump full tombstone file

If tid specified, sends a request to debuggerd to dump that task.

Otherwise, starts the debuggerd server.

out of memory

/dev/input

could not get event, %s

could not get event

SIGILL

SIGABRT

SIGBUS

SIGFPE

SIGSEGV

SIGPIPE

SIGSTKFLT

SIGSTOP

ILL_ILLOPC

ILL_ILLOPN

ILL_ILLADR

ILL_ILLTRP

ILL_PRVOPC

ILL_PRVREG

ILL_COPROC

ILL_BADSTK

BUS_ADRALN

BUS_ADRERR

BUS_OBJERR

FPE_INTDIV

FPE_INTOVF

FPE_FLTDIV

FPE_FLTOVF

FPE_FLTUND

FPE_FLTRES

FPE_FLTINV

FPE_FLTSUB

SEGV_MAPERR

SEGV_ACCERR

UNKNOWN

pid: %d, tid: %d, name: %s >>> %s <<<

pid: %d, tid: %d, name: %s

#%02d %08x %08x %s (%s+%u)

#%02d %08x %08x %s (%s)

%08x %08x %s (%s+%u)

%08x %08x %s (%s)

#%02d %08x %08x %s

%08x %08x %s

backtrace:

%s

stack:

........ ........

*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***

ro.build.fingerprint

unknown

Build fingerprint: '%s'

cannot get siginfo: %s

signal %d (%s), code %d (%s), fault addr %08x

cannot get siginfo for %d: %s

memory map around fault addr %08x:

%08x-%08x %s

(no map below)

(no map for address)

(no map above)

--- --- --- --- --- --- --- --- --- --- --- --- --- --- --- ---

signal %d (%s), code %d (%s), fault addr --------

/data/tombstones

/data/tombstones/tombstone_%02d

failed to open tombstone file '%s': %s

DEBUG

waitpid failed: %s

unexpected waitpid response: n=%d, status=%08x

timed out waiting for tid=%d to die

timed out waiting for tid=%d to stop

%08x

%08lx

%s %s

memory near %.2s:

code around pc:

code around lr:

cannot get registers: %s

r0 %08x r1 %08x r2 %08x r3 %08x

r4 %08x r5 %08x r6 %08x r7 %08x

r8 %08x r9 %08x sl %08x fp %08x

ip %08x sp %08x lr %08x pc %08x cpsr %08x

d%-2d %016llx d%-2d %016llx

scr %08lx

r0r1r2r3r4r5r6r7r8r9slfpipsp

GCC: (GNU) 4.6.x-google 20120106 (prerelease)

GNU

gold 1.10

aeabi

ARM v7

.shstrtab

.interp

.dynsym

.dynstr

.hash

.rel.dyn

.rel.plt

.text

.ARM.extab

.ARM.exidx

.rodata

.preinit_array

.init_array

.fini_array

.ctors

.dynamic

.got

.bss

.comment

.note.gnu.gold-version

.ARM.attributes