This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug gdb/19811] New: register value is not correct in catchpoint syscall execve after vfork
- From: "yanghh at gmail dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Fri, 11 Mar 2016 19:12:59 +0000
- Subject: [Bug gdb/19811] New: register value is not correct in catchpoint syscall execve after vfork
- Auto-submitted: auto-generated
https://sourceware.org/bugzilla/show_bug.cgi?id=19811
Bug ID: 19811
Summary: register value is not correct in catchpoint syscall
execve after vfork
Product: gdb
Version: 7.7
Status: NEW
Severity: normal
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: yanghh at gmail dot com
Target Milestone: ---
most register values are zero, which is not correct. the tested gdb version is
7.7.1, the problem exists in the recent 7.11 too.
$ gdb -q -ex 'set follow-fork-mode child' -ex 'catch syscall execve' -ex r -ex
'info reg' -batch -
-args gcc -xc - < /dev/null
Catchpoint 1 (syscall 'execve' [59])
[New process 48981]
process 48981 is executing new program: /usr/lib/gcc/x86_64-linux-gnu/4.8/cc1
[Switching to process 48981]
Catchpoint 1 (call to syscall execve), 0x00007ffff7ddb2d0 in _start () from
/lib64/ld-linux-x86-64.so.2
rax 0x0 0
rbx 0x0 0
rcx 0x0 0
rdx 0x0 0
rsi 0x0 0
rdi 0x0 0
rbp 0x0 0x0
rsp 0x7fffffffe390 0x7fffffffe390
r8 0x0 0
r9 0x0 0
r10 0x0 0
r11 0x0 0
r12 0x0 0
r13 0x0 0
r14 0x0 0
r15 0x0 0
rip 0x7ffff7ddb2d0 0x7ffff7ddb2d0 <_start>
eflags 0x200 [ IF ]
cs 0x33 51
ss 0x2b 43
ds 0x0 0
es 0x0 0
fs 0x0 0
gs 0x0 0
gcc: internal compiler error: Killed (program cc1)
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-4.8/README.Bugs> for instructions.
--
You are receiving this mail because:
You are on the CC list for the bug.