Re: [Geany-Devel] About Malloc memory for each tab?

2015-10-27 Thread Thomas Martitz
Am 24.10.2015 um 02:30 schrieb Matthew Brush: FWIW, doc->id is basically not very useful, it just tells the index into some internal array of GeanyDocument objects, but is not unique to each document/tab per se (it gets recycled for new documents and such). doc->id is unique these days,

Re: [Geany-Devel] About Malloc memory for each tab?

2015-10-25 Thread Pengfei Sun
Hi Matthew, Thanks for your explanation about the process of page switch. It is very helpful for me. I want to recognize all malloc or new memory allocation functions related with one tab page. I hope to log all this memory allocation functions information related with this one tab no any other

Re: [Geany-Devel] About Malloc memory for each tab?

2015-10-23 Thread Pengfei Sun
Hi Lex, I have one question about tab switch in the geany. I know the different tab has different doc->id. I think there is only one thread which manages all tabs, right? I wonder when we switch different tabs to edit the document. How does geany manage or recognize different tabs?

Re: [Geany-Devel] About Malloc memory for each tab?

2015-10-23 Thread Matthew Brush
On 15-10-23 09:21 AM, Pengfei Sun wrote: Hi Lex, I have one question about tab switch in the geany. I know the different tab has different doc->id. I think there is only one thread which manages all tabs, right? I wonder when we switch different tabs to edit the document. How does geany manage

Re: [Geany-Devel] About Malloc memory for each tab?

2015-10-23 Thread Lex Trotman
On 24 October 2015 at 02:21, Pengfei Sun wrote: > Hi Lex, > > I have one question about tab switch in the geany. I know the different tab > has different doc->id. I think there is only one thread which manages all > tabs, right? I wonder when we switch different tabs to

Re: [Geany-Devel] About Malloc memory for each tab?

2015-10-16 Thread Pengfei Sun
Thanks Lex. On Thu, Oct 15, 2015 at 5:33 PM, Lex Trotman wrote: > On 16 October 2015 at 06:42, Pengfei Sun wrote: > > Hi Lex, > > > > I checked again the gap buffer and heap memory dump. I made mistakes last > > time. scintilla_send_message returned the

Re: [Geany-Devel] About Malloc memory for each tab?

2015-10-15 Thread Lex Trotman
On 16 October 2015 at 06:42, Pengfei Sun wrote: > Hi Lex, > > I checked again the gap buffer and heap memory dump. I made mistakes last > time. scintilla_send_message returned the virtual address which was the > address of text in the heap. However, I also found parts of

Re: [Geany-Devel] About Malloc memory for each tab?

2015-10-15 Thread Pengfei Sun
Hi Lex, I checked again the gap buffer and heap memory dump. I made mistakes last time. scintilla_send_message returned the virtual address which was the address of text in the heap. However, I also found parts of text (each line) which locate in different address in the heap. So I made the

Re: [Geany-Devel] About Malloc memory for each tab?

2015-10-14 Thread Lex Trotman
On 13 October 2015 at 04:43, Pengfei Sun wrote: > Hi Lex, > > Thanks for you hint about scintilla. Matthew also mentioned to use the > scintilla. I tried his patch, but there is still one problem about the > address of buffer. I don't know why the address of output is not

Re: [Geany-Devel] About Malloc memory for each tab?

2015-10-12 Thread Pengfei Sun
Hi Matthew, Thanks for your illustration and patch. I have patched the code to geany source code. Now I can get the memory address of buffer as your mentioned. When I tried your patch, I also dumped the whole memory and checked the heap memory. For example, I wrote several characters in one line.

Re: [Geany-Devel] About Malloc memory for each tab?

2015-10-12 Thread Pengfei Sun
Hi Lex, Thanks for you hint about scintilla. Matthew also mentioned to use the scintilla. I tried his patch, but there is still one problem about the address of buffer. I don't know why the address of output is not consistent with address of buffer in the dumped heap memory? Best Regards,

Re: [Geany-Devel] About Malloc memory for each tab?

2015-10-09 Thread Matthew Brush
On 15-10-09 04:43 PM, Matthew Brush wrote: On 15-10-09 03:42 PM, Pengfei Sun wrote: [...] Do you have any further suggestions for my case? I made a quick and dirty patch that will log on the terminal wherever in (virtual) memory the buffer is stored, whenever it moves, per-file. See

Re: [Geany-Devel] About Malloc memory for each tab?

2015-10-09 Thread Lex Trotman
On 10 October 2015 at 09:12, Lex Trotman wrote: > On 10 October 2015 at 08:42, Pengfei Sun wrote: >> Hi Lex, >> >> Thanks for your suggestions. >> >> I work on memory forensics. My part of project is to locate memory of the >> sensitive data. For example,

Re: [Geany-Devel] About Malloc memory for each tab?

2015-10-09 Thread Matthew Brush
On 15-10-09 03:42 PM, Pengfei Sun wrote: Hi Lex, Thanks for your suggestions. I work on memory forensics. My part of project is to locate memory of the sensitive data. For example, when I use the geany open one sensitive file, and the content will be in the memory (heap). I hope I can locate

Re: [Geany-Devel] About Malloc memory for each tab?

2015-10-09 Thread Lex Trotman
On 10 October 2015 at 05:05, Pengfei Sun wrote: > Dear All, > > I am always using geany, but now this is the first time I prepare to look at > geany source code. I have one question about memory allocation. When we open > one new file, there will be one new window in geany.

Re: [Geany-Devel] About Malloc memory for each tab?

2015-10-09 Thread Lex Trotman
On 10 October 2015 at 08:42, Pengfei Sun wrote: > Hi Lex, > > Thanks for your suggestions. > > I work on memory forensics. My part of project is to locate memory of the > sensitive data. For example, when I use the geany open one sensitive file, > and the content will be in

Re: [Geany-Devel] About Malloc memory for each tab?

2015-10-09 Thread Pengfei Sun
Hi Lex, Thanks for your suggestions. I work on memory forensics. My part of project is to locate memory of the sensitive data. For example, when I use the geany open one sensitive file, and the content will be in the memory (heap). I hope I can locate all memory related this sensitive file. And