On 2016-07-15 21:39, tcak wrote:
Never used D on Xcode, nor I knew it was possible.
Well, when it comes to using the debugger in Xcode or profiling using
Instruments both can load any application. Although you won't get any
demangling in the debugger but if you and the source files to an
On 07/15/2016 03:42 PM, tcak wrote:
If it is about speed, we can still use a public shared memory for that
purpose. So, statistical messages can be written in shared memory, and
other program reads from that to get those messages. A suitable
communication protocol can be implemented in way. At
On Friday, 15 July 2016 at 17:04:35 UTC, Andrei Alexandrescu
wrote:
On 07/15/2016 12:31 PM, tcak wrote:
Do you know about --profile=gc?
1. Never worked for me in a multithreaded program.
Could you please give it another look. Walter fixed it
relatively recently.
Hmm, I will check it
On Friday, 15 July 2016 at 19:22:41 UTC, Jacob Carlborg wrote:
On 2016-07-15 18:14, tcak wrote:
It is great to see memory usage on Xcode while running an iOS
app.
Have you tried to run a D application inside Xcode to get the
same information? Or is it not available due to the GC?
Never
On 2016-07-15 18:14, tcak wrote:
It is great to see memory usage on Xcode while running an iOS app.
Have you tried to run a D application inside Xcode to get the same
information? Or is it not available due to the GC?
--
/Jacob Carlborg
On 07/15/2016 12:31 PM, tcak wrote:
Do you know about --profile=gc?
1. Never worked for me in a multithreaded program.
Could you please give it another look. Walter fixed it relatively recently.
2. I am not able to retrieve that data on runtime by another application
to see close to
On Friday, 15 July 2016 at 16:21:15 UTC, Jack Stouffer wrote:
On Friday, 15 July 2016 at 16:14:39 UTC, tcak wrote:
It is great to see memory usage on Xcode while running an iOS
app.
What I thought is that:
1. GC knows available heap memory locations and their length.
2. GC can detect what
On Friday, 15 July 2016 at 16:14:39 UTC, tcak wrote:
It is great to see memory usage on Xcode while running an iOS
app.
What I thought is that:
1. GC knows available heap memory locations and their length.
2. GC can detect what parts of heap is in use.
3. A program can create a file to write
It is great to see memory usage on Xcode while running an iOS app.
What I thought is that:
1. GC knows available heap memory locations and their length.
2. GC can detect what parts of heap is in use.
3. A program can create a file to write (stdout, stderr, etc.)
So, when desired (e.g. use of
