Hi Mark,

On Fri, 2026-10-23 at 07:20 -0700, Mark Harris wrote:
> Mark Wielaard wrote:
> 
> > > 10 failed because "Max number of guard pages is too low":
> > > memcheck/tests/err_disable4              (stderr)
> > > memcheck/tests/thread_alloca             (stderr)
> > > helgrind/tests/annotate_smart_pointer    (stderr)
> > > helgrind/tests/pth_barrier3              (stderr)
> > > drd/tests/annotate_smart_pointer         (stderr)
> > > drd/tests/concurrent_close               (stderr)
> > > drd/tests/pth_barrier3                   (stderr)
> > > drd/tests/pth_barrier_thr_cr             (stderr)
> > > drd/tests/pth_create_chain               (stderr)
> > > drd/tests/swapcontext                    (stderr)
> > 
> > I don't understand these. Would you be able to recompile with this
> > patch:
> > 
> > diff --git a/coregrind/m_aspacemgr/aspacemgr-linux.c 
> > b/coregrind/m_aspacemgr/aspacemgr-linux.c
> > index 6ede41a0151f..a9ee0e3e670d 100644
> > --- a/coregrind/m_aspacemgr/aspacemgr-linux.c
> > +++ b/coregrind/m_aspacemgr/aspacemgr-linux.c
> > @@ -1107,7 +1107,7 @@ static void guard_page_install ( Addr addr ) {
> >     Addr addr_aligned = addr & ~(VKI_PAGE_SIZE - 1);
> >     if (nguardpages_used >= VG_N_GUARDS) {
> >        VG_(printf)("Use --max-guard-pages=INT to specify a larger number 
> > of\n"
> > -                  "guard pages and rerun valgrind\n");
> > +                  "guard pages (current %u) and rerun valgrind\n", 
> > VG_N_GUARDS);
> >        VG_(core_panic)("Max number of guard pages is too low");
> >     }
> >     // bisect
> > 
> > We might be not be initializing VG_N_GUARDS correctly.  Or something
> > in your environment installs lots (500+?) guardpages for some reason.
> 
> With this patch, tests like memcheck/tests/err_disable4 show:
> Use --max-guard-pages=INT to specify a larger number of
> guard pages (current 500) and rerun valgrind
> 
> I just noticed that 9 of these 10 are also listed as failures in your
> Fedora aarch64 run.  Are yours failing for a different reason?

O darn. I hadn't looked clearly at those results apparently.
Yes, they fail in the same way. Looks like this is an arm64 specific
issue. I have it reproduced now. Trying to figure out why this is
happening.

Thanks,

Mark


_______________________________________________
Valgrind-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/valgrind-users

Reply via email to