Date: Mon, 14 Jan 2013 19:39:16 -0800 From: Garrett Cooper <yanegomi@gmail.com> To: FreeBSD Current <freebsd-current@freebsd.org> Cc: kib@FreeBSD.org Subject: Re: ktrace -d broken on current/stable-9 Message-ID: <4099FD6F-1F1B-481F-ABE7-F710551768CE@gmail.com> In-Reply-To: <4850A09B-A054-4B38-891C-06673F7195B2@gmail.com> References: <4850A09B-A054-4B38-891C-06673F7195B2@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
BTW, the brokenness can be seen in the fact that the PID does = not change across execs, but it seems to affect output as well as I was = not able to see syscall output from write when it printed out = "Executing" as shown in the snippet below. Thanks, -Garrett On Jan 14, 2013, at 6:48 PM, Garrett Cooper wrote: > I tried using ktrace on a kernel compiled a week ago, and it = appears to not be following forks like it should on amd64: >=20 > # ktrace -d ./regress -l > rename_file move_files_into_dir move_file_from_dir_to_file = move_file_from_dir_to_existing_file move_file_from_dir_to_existing_dir = move_file_from_dir_to_dir rename_dir move_dir_to_dir_name = move_dir_to_dir move_file_from_dir_to_empty_dir = move_file_from_dir_to_nonempty_dir move_dir_to_existing_file = move_file_from_dir_to_dir move_file_from_dir_to_dir = move_file_from_dir_to_dir move_fifo_from_dir_to_dir > rename_file move_files_into_dir move_file_from_dir_to_file = move_file_from_dir_to_existing_file move_file_from_dir_to_existing_dir = move_file_from_dir_to_dir rename_dir move_dir_to_dir_name = move_dir_to_dir move_file_from_dir_to_empty_dir = move_file_from_dir_to_nonempty_dir move_dir_to_existing_file = move_file_from_dir_to_dir move_file_from_dir_to_dir = move_file_from_dir_to_dir move_fifo_from_dir_to_dir = rename_file_cross_device move_files_into_dir_cross_device = move_file_from_dir_to_file_cross_device = move_file_from_dir_to_existing_file_cross_device = move_file_from_dir_to_existing_dir_cross_device = move_file_from_dir_to_dir_cross_device rename_dir_cross_device = move_dir_to_dir_name_cross_device move_dir_to_dir_cross_device = move_file_from_dir_to_empty_dir_cross_device = move_file_from_dir_to_nonempty_dir_cross_device = move_dir_to_existing_file_cross_device = move_file_from_dir_to_dir_cross_device = move_file_from_dir_to_dir_cross_device = move_file_from_dir_to_dir_cross_device = move_fifo_from_dir_to_dir_cross_device > Content-Type: application/X-atf-tp; version=3D"1" >=20 > ident: rename_file > descr: Rename file >=20 > ident: move_files_into_dir > descr: Move files into directory >=20 > Executing command [ mv 1/2/3/fa fb ] >=20 > # uname -a > FreeBSD fuji-current.local 10.0-CURRENT FreeBSD 10.0-CURRENT #2 = r+73182f4: Sun Jan 6 13:41:52 PST 2013 = root@fuji-current.local:/usr/obj/usr/src/sys/FUJI i386 > # kdump | awk '$1 ~ /25/' | sort -u -k 1 -n > 25195 ktrace RET ktrace 0 >=20 > Not sure how it broke, but it was working a couple months ago = (in particular I remember it working either around October or November), = and the bug seems to have worked its way back to 9-STABLE (I'm running = into the same problem if I do ktrace -d, enter a shell, then exec = another shell from that shell). Haven't spent the time to bisect the = commits looking for the culprit (yet), but if need be I'll trace down = the culprit sometime this week. > truss works, so it doesn't seem like ptrace(2) is broken. > Thanks, > -Garrett
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4099FD6F-1F1B-481F-ABE7-F710551768CE>