https://bugs.kde.org/show_bug.cgi?id=395416
Bug ID: 395416
Summary: --log-file output isn't split correctly after call
vgdb
Product: valgrind
Version: 3.13.0
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: memcheck
Assignee: jsew...@acm.org
Reporter: opera.wang+...@gmail.com
Target Milestone: ---
To work around bug 395414 , we call vgdb periodically to see if the application
calls exit() but does not quit.
However, it turns out call vgdb will make split log file does not work
correctly, if we do not call vgdb, the fix in bug 162848 works fine. But if we
call vgdb on parent process eg 29351:
/depotbld/RHEL5.5/tools/valgrind/3.13.0-rhel-6/bin/vgdb --pid=29351 v.info
scheduler
Then child process 31414's log file only contains a few start information like
valgrind command line options, and the left log will mixed in 29351's log:
--29351-- REDIR: 0xfe25cc0 (libc.so.6:strcspn) redirected to 0xa564730
(_vgnU_ifunc_wrapper)
--29351-- REDIR: 0xfed89e0 (libc.so.6:__strcspn_sse42) redirected to 0xa7700b0
(strcspn)
==31414== Reset valgrind output to log (reset_after_fork)
==31414== Warning: invalid file descriptor -1 in syscall close()
==31414== at 0xB48F870: __close_nocancel (in /lib64/libpthread-2.12.so)
--
You are receiving this mail because:
You are watching all bug changes.
