From: Simon Glass <sjg@chromium.org>
To: u-boot@lists.denx.de
Subject: [PATCH 3/4] doc: sandbox: Document how to run sandbox with valgrind
Date: Wed, 5 May 2021 17:32:58 -0600 [thread overview]
Message-ID: <CAPnjgZ3W-HEDgb2+XuAca2+fR9L6hQgo5mqxrDeEFR00pSEpwg@mail.gmail.com> (raw)
In-Reply-To: <0bc3a790-b34c-3604-798f-fbd5afaf9ed6@gmail.com>
Hi Sean,
On Tue, 4 May 2021 at 17:23, Sean Anderson <seanga2@gmail.com> wrote:
>
> On 5/4/21 11:26 AM, Simon Glass wrote:
> > Hi Sean,
> >
> > On Sun, 2 May 2021 at 20:55, Sean Anderson <seanga2@gmail.com> wrote:
> >>
> >> This documents how to get more detailed results from valgrind made possible
> >> by the last two commits.
> >>
> >> Signed-off-by: Sean Anderson <seanga2@gmail.com>
> >> ---
> >>
> >> doc/arch/sandbox.rst | 14 ++++++++++----
> >> 1 file changed, 10 insertions(+), 4 deletions(-)
> >
> > Reviewed-by: Simon Glass <sjg@chromium.org>
> >
> > This looks good. I wonder if CONFIG_VALGRIND could become a build
> > variable as well, so you don't need to update the CONFIG?
>
> Are there any existing examples of things which work like that?
Yes, see 'DEVICE_TREE' in Makefile
Regards,
Simon
next prev parent reply other threads:[~2021-05-05 23:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-03 2:55 [PATCH 0/4] malloc: Enable profiling dlmalloc with valgrind Sean Anderson
2021-05-03 2:55 ` [PATCH 1/4] Add valgrind headers to U-Boot Sean Anderson
2021-05-04 15:26 ` Simon Glass
2021-05-03 2:55 ` [PATCH 2/4] malloc: Annotate allocator for valgrind Sean Anderson
2021-05-04 15:26 ` Simon Glass
2021-05-03 2:55 ` [PATCH 3/4] doc: sandbox: Document how to run sandbox with valgrind Sean Anderson
2021-05-04 15:26 ` Simon Glass
2021-05-04 23:23 ` Sean Anderson
2021-05-05 23:32 ` Simon Glass [this message]
2021-05-03 2:55 ` [PATCH 4/4] malloc: Fix sbrk clearing memory after freeing it instead of before Sean Anderson
2021-05-04 15:26 ` Simon Glass
2021-05-04 23:32 ` Sean Anderson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAPnjgZ3W-HEDgb2+XuAca2+fR9L6hQgo5mqxrDeEFR00pSEpwg@mail.gmail.com \
--to=sjg@chromium.org \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.