Paul Dufresne <dufres...@zoho.com> writes: > ---- Le ven., 26 févr. 2021 23:29:01 -0500 Jessica Clarke <jrt...@debian.org> > écrit ---- >> > > I'd advise you to not delve too deeply into malloc. This is likely a > > buffer overflow that then corrupts the (inline) state maintained by > > malloc, so you really need to be looking at vim. > > > > Jess > > I have an idea. > I could replace the assert by a printf of the address of the pointer. > > Then if I could generate a map of vim, I could figure out approximately that > the buffer overflowing is just before that address? > > Frankly, not knowing exactly what I am doing... ;-)
You may not know exactly what you're doing, but you are currently the world's leading expert in fixing this particular bug. :) No offense meant to other Hurd developers. They are just busy addressing other issues. -- Joshua Branson (joshuaBPMan in #guix) Sent from Emacs and Gnus https://gnucode.me https://video.hardlimit.com/accounts/joshua_branson/video-channels https://propernaming.org "You can have whatever you want, as long as you help enough other people get what they want." - Zig Ziglar
