[Bug libc/34539] New: ptrace PTRACE_POKEUSER vs PTRACE_POKEUSR
ndesaulniers at google dot com via Glibc-bugs <[email protected]>
| Newsgroups | gmane.comp.lib.glibc.bugs |
|---|---|
| Message-ID | <[email protected]/bugzilla/> |
https://sourceware.org/bugzilla/show_bug.cgi?id=34539
Bug ID: 34539
Summary: ptrace PTRACE_POKEUSER vs PTRACE_POKEUSR
Product: glibc
Version: unspecified
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: libc
Assignee: unassigned at sourceware dot org
Reporter: ndesaulniers at google dot com
CC: drepper.fsp at gmail dot com
Target Milestone: ---
I was refactoring code in lldb and hit a breakage that I had to squint at for a
bit.
I don't know if it's a bug in glibc, per se, but I noticed that in my kernel
headers:
/usr/include/linux/ptrace.h#L17: #define PTRACE_POKEUSR 6
but in my glibc headers:
/usr/include/x86_64-linux-gnu/sys/ptrace.h#L58: PTRACE_POKEUSER = 6,
I don't know if the glibc enum variants' identifiers are supposed to match the
kernel identifiers, but it looks like there's a subtle difference in spelling
between the two: PTRACE_POKEUSR vs PTRACE_POKEUSER.
In the case of lldb, it was using PTRACE_POKEUSER (glibc), but I think I should
change it to PTRACE_POKEUSR (linux kernel).
--
You are receiving this mail because:
You are on the CC list for the bug.