This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "Hurd".
The branch, master has been updated via b372e439e05e336d5e52aa0ce69c799c15691932 (commit) via 84932431cf4fbd494b4597105faed26ed2ac4efe (commit) via b8bce60ff16e52862ca5a3c5a6018420b4fa3cd1 (commit) via 9a1bb117c165bbedb2b75578ac71e46f2139470e (commit) via d999b70a3f395afe06d430c14fdf02a64ac28c06 (commit) from ae04256ee85fa02288f34587faad5d461ad57186 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- commit b372e439e05e336d5e52aa0ce69c799c15691932 Author: Justus Winter <4win...@informatik.uni-hamburg.de> Date: Fri Dec 13 15:25:22 2013 +0100 utils/rpctrace: fix output so that replies can be attributed to requests Currently, it is impossible to properly attribute response messages to requests. Even though rpctrace is single-threaded, its tracee may not. Or there might be more than one tracee. In any such case it is not guaranteed that the reply message we just processed is for the request we just printed. Fix this by printing ellipsis with the port name, so that reply messages can be properly attributed: task129(pid3312)->mach_port_allocate (3) ...134 task129(pid3312)->mach_port_deallocate (pn{ 1}) ...160 134... = 0 pn{ 30} 160... = 0 * utils/rpctrace.c (last_reply_port): New variable. (print_ellipsis): New function. (print_request_header): Optionally print ellipsis and update last_reply_port. (print_reply_header): Likewise. commit 84932431cf4fbd494b4597105faed26ed2ac4efe Author: Justus Winter <4win...@informatik.uni-hamburg.de> Date: Fri Dec 13 12:57:55 2013 +0100 utils/rpctrace: escape non-printable characters in strings * utils/rpctrace.c (escape_sequences): New char array mapping characters to their escape sequence. (print_data): Escape non-printable characters when printing strings. commit b8bce60ff16e52862ca5a3c5a6018420b4fa3cd1 Author: Justus Winter <4win...@informatik.uni-hamburg.de> Date: Wed Dec 11 12:56:47 2013 +0100 utils/rpctrace: handle MACH_MSG_TYPE_PORT_SEND rights in trace_and_forward This allows one to rpctrace processes doing select(2). * utils/rpctrace.c (trace_and_forward): Handle MACH_MSG_TYPE_PORT_SEND rights. commit 9a1bb117c165bbedb2b75578ac71e46f2139470e Author: Justus Winter <4win...@informatik.uni-hamburg.de> Date: Wed Dec 11 11:35:39 2013 +0100 utils/rpctrace: generalize tracing code Currently, rpctrace dies if a tracee uses select(2) because it asserts that reply_type is a MACH_MSG_TYPE_PORT_SEND_ONCE right. Generalize the code surrounding the failing assertion. * utils/rpctrace.c (trace_and_forward): Generalize code by switching over reply_type. commit d999b70a3f395afe06d430c14fdf02a64ac28c06 Author: Justus Winter <4win...@informatik.uni-hamburg.de> Date: Wed Dec 11 12:51:10 2013 +0100 utils/rpctrace: generalize code in rewrite_right * utils/rpctrace.c (rewrite_right): Generalize the code so we can use rewrite_right to rewrite MACH_MSG_TYPE_PORT_SEND rights for non-rpc ports. ----------------------------------------------------------------------- Summary of changes: utils/rpctrace.c | 124 +++++++++++++++++++++++++++++++++++++++++++---------- 1 files changed, 100 insertions(+), 24 deletions(-) hooks/post-receive -- Hurd