Re: ktrace -d broken on current/stable-9

	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:
> 
> # 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_di
 r_to_dir_cross_device
> Content-Type: application/X-atf-tp; version="1"
> 
> ident: rename_file
> descr: Rename file
> 
> ident: move_files_into_dir
> descr: Move files into directory
> 
> Executing command [ mv 1/2/3/fa fb ]
> 
> # 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
> 
> 	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

_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"