Maybe consider rpmalloc

[Mark Geisert]

Jon Turney wrote:
> On 14/04/2021 09:19, Mark Geisert wrote:
>> I need to identify what's being hit within ntdll.dll.  Is it one or two 
>> routines, or just hot locks.  So that means getting the correct PDB file from 
>> the MS Symbol Server and working with Windows tools I'm unfamiliar with.  Sigh, 
>> in an earlier life I had a gdb that we'd taught how to work 
> 
> Yes, this would indeed be a very useful thing to have in gdb.
> 
> I'm not aware of any public work in that direction, though.
> 
>> with PDB files; dunno if I could resurrect that.  Profiling the Cygwin DLL 
>> itself, call profiling I mean, might lead somewhere as well.
> 
> In the past I've had some success with using the Very Sleepy profiler ([1]), which 
> can use both PDB and DWARF symbols, on cygwin executables.
> 
> [1] https://github.com/VerySleepy/verysleepy

Thanks for that link, Jon.  That tool is potentially very useful.  Are you sure it 
understands DWARF though?  It seems to show only a subset of cygwin1.dll symbols 
but I can't immediately tell why those and not others.  Perhaps they're just the 
unmangled names present in the COFF symbol table?

Did you do anything in particular to assist it with debugging Cygwin exes?  Like 
adding to the Symbol Cache it builds?  I only see PDB files in its cache so far.

I think building a "fake" PDB file for cygwin1.dll might be good enough, but if 
there's an easier way I'd love to hear it.
Thanks again,

..mark