[prev in list] [next in list] [prev in thread] [next in thread]
List: boost
Subject: Re: [boost] boost log memory leak? Maybe it is my wrong.
From: "Jefferyliangmh"<liang_mh () 163 ! com>
Date: 2015-11-16 3:49:27
Message-ID: 18add86c.12b3ea.1510e696736.Coremail.liang_mh () 163 ! com
[Download RAW message or body]
[Attachment #2 (text/plain)]
Many thanks andrey.semashev's reply. I send my demo application codes in \
BoostDemo.rar file. "logger" is my wrapped module by win32 dll. "BoostDemo" is my \
MFC test application, call logger code written in CMainFrame::CMainFrame() fuction, \
like this : AppLogger::log("this is test message").
Memory leak display in output windows when compiled BoostDemo application.
2015-11-16
2015-11-16
Jefferyliangmh
发件人:boost-request@lists.boost.org
发送时间:2015-11-16 01:00
主题:Boost Digest, Vol 4908, Issue 1
收件人:"boost"<boost@lists.boost.org>
抄送:
Send Boost mailing list submissions to
boost@lists.boost.org
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.boost.org/mailman/listinfo.cgi/boost
or, via email, send a message with subject or body 'help' to
boost-request@lists.boost.org
You can reach the person managing the list at
boost-owner@lists.boost.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Boost digest..."
The boost archives may be found at: http://lists.boost.org/Archives/boost/
Today's Topics:
1. boost log memory leak? Maybe it is my wrong.
(=?UTF-8?B?5qKB5piO6L6J?=)
2. Re: boost log memory leak? Maybe it is my wrong. (Andrey Semashev)
3. Re: checking __INTEL_COMPILER == 9999 (Blower, Melanie)
4. Re: checking __INTEL_COMPILER == 9999 (Edward Diener)
----------------------------------------------------------------------
Message: 1
Date: Sat, 14 Nov 2015 19:31:28 +0800
From: "=?UTF-8?B?5qKB5piO6L6J?="<liang_mh@163.com>
To: "boost"<boost@lists.boost.org>
Subject: [boost] boost log memory leak? Maybe it is my wrong.
Message-ID: <220730f2.126658.15105c3ab0c.Coremail.liang_mh@163.com>
Content-Type: text/plain; charset="UTF-8"
Way I want to use win32 dynamic link library encapsulates the boost.log, the wrapper \
DLL in MFC MSVC 2015 calls, memory leak in output window prompt; The same library in \
a console program calls, no such problems. I am very depressed. Who can help me?
2015-11-14
???
------------------------------
Message: 2
Date: Sun, 15 Nov 2015 00:05:28 +0300
From: Andrey Semashev <andrey.semashev@gmail.com>
To: "boost@lists.boost.org" <boost@lists.boost.org>
Subject: Re: [boost] boost log memory leak? Maybe it is my wrong.
Message-ID:
<CAEhD+6BH=Lnw1ghLwOVarXbYGDBqoNygzcWnML+TtU7mVbB1zQ@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
On Sat, Nov 14, 2015 at 2:31 PM, ??? <liang_mh@163.com> wrote:
> Way I want to use win32 dynamic link library encapsulates the boost.log, the \
> wrapper DLL in MFC MSVC 2015 calls, memory leak in output window prompt; The same \
> library in a console program calls, no such problems. I am very depressed. Who can \
> help me?
If you work with Boost.Log the same way in both cases then it's likely
a problem in your code and not the library. Otherwise I can't help
without a minimal working code sample.
------------------------------
Message: 3
Date: Sun, 15 Nov 2015 13:05:27 +0000
From: "Blower, Melanie" <melanie.blower@intel.com>
To: "boost@lists.boost.org" <boost@lists.boost.org>
Subject: Re: [boost] checking __INTEL_COMPILER == 9999
Message-ID:
<B3584E72CFEBED439A3ECA9BCE67A4EF40258FCC@fmsmsx116.amr.corp.intel.com>
Content-Type: text/plain; charset="us-ascii"
Thanks for all your suggestions and replies, I will work it on the Intel side. To \
Edward, at the bottom of my first message there's info about one of the failure \
modes.
--Melanie
------------------------------
Message: 4
Date: Sun, 15 Nov 2015 10:43:25 -0500
From: Edward Diener <eldiener@tropicsoft.com>
To: boost@lists.boost.org
Subject: Re: [boost] checking __INTEL_COMPILER == 9999
Message-ID: <n2a971$msb$1@ger.gmane.org>
Content-Type: text/plain; charset=windows-1252; format=flowed
On 11/15/2015 8:05 AM, Blower, Melanie wrote:
> Thanks for all your suggestions and replies, I will work it on the Intel side. To \
> Edward, at the bottom of my first message there's info about one of the failure \
> modes.
Thanks, I see that now.
------------------------------
Subject: Digest Footer
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
------------------------------
End of Boost Digest, Vol 4908, Issue 1
**************************************
["BoostDemo.rar" (application/octet-stream)]
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic