https://bugs.kde.org/show_bug.cgi?id=479191
Bug ID: 479191
Summary: vgdb is blocked after several tries
Classification: Developer tools
Product: valgrind
Version: 3.22 GIT
Platform: Other
OS: Other
Status: REPORTED
Severity: normal
Priority: NOR
Component: massif
Assignee: n...@valgrind.org
Reporter: dark_foo...@yahoo.fr
Target Milestone: ---
Hello,
I have a strange behavior with a specific program, on the second vgdb request,
the vgdb is blocking.
I runned with "vgdb -d" to have more log, maybe the current log would be clever
for someone ?
SUMMARY
***
valgrind '--tool=massif' '--time-unit=ms' '--vgdb=yes' '--vgdb-error=0'
'--trace-children=yes' '--threshold=0.01' '--detailed-freq=1'
'--massif-out-file=/tmp/massif.out' '--peak-inaccuracy=0.0'
'--max-snapshots=1000' my_progs
==4685== Massif, a heap profiler
==4685== Copyright (C) 2003-2017, and GNU GPL'd, by Nicholas Nethercote
==4685== Using Valgrind-3.22.0.GIT and LibVEX; rerun with -h for copyright info
==4685== Command:
==4685== (action at startup) vgdb me ...
==4685== target remote | /usr/libexec/valgrind/../../bin/vgdb --pid=4685
//first vgdb OK
vgdb -d '--cmd-time-out=2' detailed_snapshot
/tmp/massif2023-12-30_17-56-45_0.out
17:57:08.067721 searching pid in directory /tmp/ format
/tmp/vgdb-pipe-from-vgdb-to-
17:57:08.069624 check_trial 0
17:57:08.070003 vgdb: using /tmp/vgdb-pipe-from-vgdb-to-5122-by-root-on-???
/tmp/vgdb-pipe-to-vgdb-from-5122-by-root-on-???
/tmp/vgdb-pipe-shared-mem-vgdb-5122-by-root-on-???
17:57:08.070295 opening /tmp/vgdb-pipe-from-vgdb-to-5122-by-root-on-??? write
to pid
17:57:08.070511 opened /tmp/vgdb-pipe-from-vgdb-to-5122-by-root-on-??? write to
pid fd 4
17:57:08.070653 opening /tmp/vgdb-pipe-to-vgdb-from-5122-by-root-on-??? read
cmd result from pid
17:57:08.070755 opened /tmp/vgdb-pipe-to-vgdb-from-5122-by-root-on-??? read cmd
result from pid fd 5
sending command detailed_snapshot /tmp/massif2023-12-30_17-56-45_0.out to pid
5122
17:57:08.072446 OK packet rcvd
17:57:08.072597 nr received signals: sigint 0 sigterm 0 sighup 0 sigpipe 0
17:57:08.072647 joining with invoke_gdbserver_in_valgrind_thread
//Second vgdb blocked
vgdb -d '--cmd-time-out=2' detailed_snapshot
/tmp/massif2023-12-30_17-56-45_1.out
18:02:11.219325 searching pid in directory /tmp/ format
/tmp/vgdb-pipe-from-vgdb-to-
18:02:11.219495 check_trial 0
18:02:11.219752 vgdb: using /tmp/vgdb-pipe-from-vgdb-to-5122-by-root-on-???
/tmp/vgdb-pipe-to-vgdb-from-5122-by-root-on-???
/tmp/vgdb-pipe-shared-mem-vgdb-5122-by-root-on-???
18:02:11.220031 opening /tmp/vgdb-pipe-from-vgdb-to-5122-by-root-on-??? write
to pid
18:02:11.220079 opened /tmp/vgdb-pipe-from-vgdb-to-5122-by-root-on-??? write to
pid fd 4
18:02:11.220127 opening /tmp/vgdb-pipe-to-vgdb-from-5122-by-root-on-??? read
cmd result from pid
18:02:11.320018 IO for command started
18:02:11.421249 waitstopped attach main pid before waitpid signal_expected 19 -
status 0x137f WIFSTOPPED 19
18:02:11.461675 examining thread entries from tid 1 to tid 499
18:02:11.461912 found tid 1 status VgTs_WaitSys lwpid 5122
18:02:11.461963 found tid 2 status VgTs_WaitSys lwpid 5171
18:02:11.461986 attach_thread PTRACE_ATTACH pid 5171
18:02:11.462028 waitstopped attach_thread before waitpid signal_expected 19
18:02:11.463665 after waitpid pid 5171 p 5171 status 0x137f WIFSTOPPED 19
18:02:11.463838 found tid 3 status VgTs_WaitSys lwpid 5274
18:02:11.463887 attach_thread PTRACE_ATTACH pid 5274
18:02:11.463924 waitstopped attach_thread before waitpid signal_expected 19
18:02:11.463953 after waitpid pid 5274 p 5274 status 0x137f WIFSTOPPED 19
18:02:11.463986 found tid 4 status VgTs_WaitSys lwpid 5184
18:02:11.464069 attach_thread PTRACE_ATTACH pid 5184
18:02:11.495196 waitstopped attach_thread before waitpid signal_expected 19
18:02:11.496582 after waitpid pid 5184 p 5184 status 0x137f WIFSTOPPED 19
18:02:11.496806 found tid 5 status VgTs_WaitSys lwpid 5204
CH pid 5204
18:02:11.496951 waitstopped attach_thread before waitpid signal_expected 19
18:02:11.497011 after waitpid pid 5204 p 5204 status 0x137f WIFSTOPPED 19
18:02:11.501070 getregs regs_bsz 72
18:02:11.501129 PTRACE_GETREGSET defined, not used (yet?) by vgdb
18:02:11.501151 getregs PTRACE_GETREGS
18:02:11.501173 detected a working PTRACE_GETREGS
18:02:11.501195 setregs regs_bsz 72
18:02:11.501216 setregs PTRACE_SETREGS
18:02:11.501237 PTRACE_CONT to invoke
18:02:11.501261 waitstopped waitpid status after PTRACE_CONT to invoke before
waitpid signal_expected 19
--
You are receiving this mail because:
You are watching all bug changes.
