Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Valgrind News #251

Closed
wants to merge 4 commits into from
Closed

Valgrind News #251

wants to merge 4 commits into from

Conversation

paulfloyd
Copy link
Contributor

No description provided.

Copy link
Contributor

@pauamma pauamma left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One sentence per line, but can be fixed later in the editorial pipeline unless you have other changes coming. Otherwise LGTM.

@paulfloyd
Copy link
Contributor Author

One sentence per line, but can be fixed later in the editorial pipeline unless you have other changes coming. Otherwise LGTM.

Just the valgrind-devel version and date when the patch lands.

Copy link
Member

@lsalvadore lsalvadore left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have made a small suggestion for the title.

I also suggest using some kind of special fonts for function names and similar things to improve readability (e.g. _memcheck_), but if you want to keep it as it is it is fine.

@@ -0,0 +1,22 @@
=== Valgrind - valgrind-devel updated for FreeBSD 15
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suggest

Suggested change
=== Valgrind - valgrind-devel updated for FreeBSD 15
=== Valgrind: valgrind-devel updated for FreeBSD 15

or

Suggested change
=== Valgrind - valgrind-devel updated for FreeBSD 15
=== Valgrind -- valgrind-devel updated for FreeBSD 15

Comment on lines 12 to 16
memcheck has been enhanced with some more checks. It will now report usage of realloc with a size of zero.
Such usage is not portable and is deprecated (C23 will make it Undefined Behaviour). memcheck
now validates the values used for alignment and sized delete for memalign, posix_memalign, aligned_alloc
and all aligned and sized overloads of operator new and operator delete. Reading DWARF debuginfo is
now done in a lazy manner which can improve performance.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
memcheck has been enhanced with some more checks. It will now report usage of realloc with a size of zero.
Such usage is not portable and is deprecated (C23 will make it Undefined Behaviour). memcheck
now validates the values used for alignment and sized delete for memalign, posix_memalign, aligned_alloc
and all aligned and sized overloads of operator new and operator delete. Reading DWARF debuginfo is
now done in a lazy manner which can improve performance.
`memcheck` has been enhanced with some more checks. It will now report usage of `realloc` with a size of zero.
Such usage is not portable and is deprecated (C23 will make it Undefined Behaviour).
`memcheck` now validates the values used for alignment and sized delete for `memalign`, `posix_memalign`, `aligned_alloc` and all aligned and sized overloads of operator `new` and operator `delete`.
Reading DWARF debuginfo is now done in a lazy manner, which can improve performance.

Agreed re: markup function names and the like. @paulfloyd have I caught all phrases? I don't know about DWARF.

Whilst here:

  • one sentence per line, as @pauamma suggests
  • a comma.

Comment on lines 20 to 22
Specific to FreeBSD there is support for FreeBSD 15. Two extra _umtx_op operations are now supported,
UMTX_OP_GET_MIN_TIMEOUT and UMTX_OP_SET_MIN_TIMEOUT. There is a fix for the use of
sysctl kern proc pathname with the guest pid or -1 which previously returned the path of the Valgrind host.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Specific to FreeBSD there is support for FreeBSD 15. Two extra _umtx_op operations are now supported,
UMTX_OP_GET_MIN_TIMEOUT and UMTX_OP_SET_MIN_TIMEOUT. There is a fix for the use of
sysctl kern proc pathname with the guest pid or -1 which previously returned the path of the Valgrind host.
Specific to FreeBSD there is support for FreeBSD 15. Two extra `_umtx_op` operations are now supported, `UMTX_OP_GET_MIN_TIMEOUT` and `UMTX_OP_SET_MIN_TIMEOUT`.
There is a fix for the use of sysctl `kern.proc.pathname` with the guest pid or -1, which previously returned the path of the Valgrind host.

Was kern proc pathname (with spaces) intended?

% sysctl -d kern.proc.pathname
kern.proc.pathname: Process executable path
% 

Whilst here: a comma.

Copy link
Contributor Author

@paulfloyd paulfloyd Sep 10, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd rather leave it as it is. It's not a command line sysctl. Users may use sysctl() or sysctlbyname() so I think that leaving it in a generic form is simpler.

One line per sentence and highlight keywords. Add close_range which I've sneaked in.
@lsalvadore
Copy link
Member

Merged with commit 6a6e4c9, thanks.

@lsalvadore lsalvadore closed this Sep 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants