Re: [DynInst_API:] serial parseapi problem on aurora at ANL

[James Kupsch <kupsch@xxxxxxxxxxx>]

Thanks John,

I was just writing that I believe that very same thing.  I will try the 
account reactivation page and let you know when I have an account (or 
run into problems).
Jim

On 10/10/24 11:00 AM, John Mellor-Crummey wrote:
> Jim has a deleted account at Argonne. He could apply to have his account 
> re-instated as part of the CSC250STTO11 project
> Project title:Â2.3.2.08 STTO11 HPCToolkit
>
>
>
> --
> John Mellor-CrummeyProfessor
> Dept of Computer ScienceRice University
> email: johnmc@xxxxxxxx <mailto:johnmc@xxxxxxxx>phone: 713-348-5179
>
> > On Oct 10, 2024, at 10:04 AM, Mark W. Krentel <krentel@xxxxxxxx 
> > <mailto:krentel@xxxxxxxx>> wrote:
> > Hi, does someone there have access to Aurora, the big machine at ANL?
> >
> > We've found a 560 Meg MPI .so library that dyninst doesn't parse well,
> > too slow and serialized.
> >
> > I run hpcstruct which calls ParseAPI::CodeObject::parse() which calls
> > ParseAPI::Parser::LaunchWork() which calls
> > ParseAPI::Parser::parse_frame() and then down to
> > InstructionAPI::Instruction::getCategory().
> >
> > With 16 threads, it settles in with top reporting 100% CPU utilization
> > (only one core running), and gdb reports 15 threads stuck at futex_wait().
> >
> > Both top and time(1) report max memory usage around 8 Gig. The login
> > nodes have 1TB RAM, so it's not running into swap or anything.
> >
> > It's not a new problem. Dyninst 13.0 runs the same.
> >
> > I was wondering if someone could take a look at this.
> > Aurora is still under NDA, so I'm being a bit guarded about details,
> > and I can't just copy the binary to another machine.
> > But if you can login to Aurora, then great.
> > If not, then we'll have to figure out something else.
> >
> > --Mark
> >
> >
> >
> > _______________________________________________
> > Dyninst-api mailing list
> > Dyninst-api@xxxxxxxxxxx <mailto:Dyninst-api@xxxxxxxxxxx>
> > https://lists.cs.wisc.edu/mailman/listinfo/dyninst-api
>
> _______________________________________________
> Dyninst-api mailing list
> Dyninst-api@xxxxxxxxxxx
> https://lists.cs.wisc.edu/mailman/listinfo/dyninst-api