[Github-comments] [geany] About Malloc memory for each tag? (#682)

elextr notifications at xxxxx
Thu Oct 8 21:59:00 UTC 2015


Please continue the discussion on the [mailing list](
http://www.geany.org/Support/MailingList) as requested, this is not an
issue.

On 9 October 2015 at 07:39, pfsun <notifications at github.com> wrote:

> Thanks your suggestion.
>
> g_malloc is one wrapper of malloc. If I track malloc, I think I can get all
> memory allocations, right?
> According to my observation, each tab for one file is related with one
> thread, right? So if I can track all memory allocation of this thread, I
> can get all memory allocation for this file, right?
>
> Thank you very much!
>
> On Thu, Oct 8, 2015 at 5:24 PM, elextr <notifications at github.com> wrote:
>
> > Unfortunately its not possible to track allocations related to one file,
> > its not even possible to track all allocations since Geany uses g_malloc
> > (IIUC you can track this, see Glib docs), libraries use libc malloc and
> > Scintilla uses C++ new.
> >
> > This sort of question is better asked on the mailing list, it is not an
> > issue. Will close and you can ask any follow up questions there.
> >
> > —
> > Reply to this email directly or view it on GitHub
> > <https://github.com/geany/geany/issues/682#issuecomment-146690281>.
> >
>
>> Reply to this email directly or view it on GitHub
> <https://github.com/geany/geany/issues/682#issuecomment-146693434>.
>


---
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/682#issuecomment-146698404
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.geany.org/pipermail/github-comments/attachments/20151008/d97d6c67/attachment.html>


More information about the Github-comments mailing list