I'd like to access some form global memory (under Windows / C++) which survives the crash of my app.
The idea behind this is:
- To have a very fast medium for logging purposes
- That can be read after the program has been restarted after a crash
How can I this? I tried several IPC things, but none of them seemed to work.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
>>Is there a way without a second process?
You could try to piggyback a system process, such as explorer.exe by inserting a DLL (see http://support.microsoft.c
>>>> To have a very fast medium for logging purposes
Did you try logging at disk, opening and closing the logfile each time? Nowadays hard disks are very very fast so you should get no performance issues for normal applications. You could use a tracing threshold which can be controled from outside of the program to control the amount of log message.
If you need faster you could use a RAM disk. It wasn't used often in these days but it still works and I bet it will work at VISTA as well.
Regards, Alex
No comment has been added to this question in more than 21 days, so it is now classified as abandoned.
I will leave the following recommendation for this question in the Cleanup Zone:
Accept: jkr {http:#18366541}
Any objections should be posted here in the next 4 days. After that time, the question will be closed.
Sean Durkin
Experts Exchange Cleanup Volunteer
Business Accounts
Answer for Membership
by: shajithchandranPosted on 2007-01-22 at 06:52:03ID: 18365565
May be you can try this, Iam not sure how helpful this be.
1. When the application is started for the first time, let the application spawn a new process. This new process will just be running in a infinite while loop. Let the new process create a shared memory region. The idea is to keep this new process as simple as possible so that it will never crash.
2. The application can attach to this shared memory. And can be used for logging.
3. When the application crashes, the shared memory region will be not destroyied since the other process is still attached.
4. When the application is restarted, it will check if the process is running. If yes, then if can again attach to the shared memory and analyse the previous logs.
Shaj