[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: daily: vim problem again
From: |
Paul Dufresne |
Subject: |
Re: daily: vim problem again |
Date: |
Fri, 26 Feb 2021 23:52:08 -0500 |
User-agent: |
Zoho Mail |
---- Le ven., 26 févr. 2021 23:29:01 -0500 Jessica Clarke <jrtc27@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... ;-)
- Re: daily: vim problem again, (continued)
- Re: daily: vim problem again, Paul Dufresne, 2021/02/26
- Re: daily: vim problem again, Samuel Thibault, 2021/02/26
- Re: daily: vim problem again, Paul Dufresne, 2021/02/26
- Re: daily: vim problem again, Samuel Thibault, 2021/02/26
- Re: daily: vim problem again, Paul Dufresne, 2021/02/26
- Re: daily: vim problem again, Jessica Clarke, 2021/02/26
- Re: daily: vim problem again, Paul Dufresne, 2021/02/26
- Re: daily: vim problem again, Samuel Thibault, 2021/02/27
- Re: daily: vim problem again, Paul Dufresne, 2021/02/26
- Re: daily: vim problem again, Jessica Clarke, 2021/02/26
- Re: daily: vim problem again,
Paul Dufresne <=
- Re: daily: vim problem again Off Topic Praise, Joshua Branson, 2021/02/27
- Re: daily: vim problem again Off Topic Praise, Samuel Thibault, 2021/02/27
- Re: daily: vim problem again, Paul Dufresne, 2021/02/28
- Re: daily: vim problem again, Samuel Thibault, 2021/02/28