U++ forum: Welcome to the forum

Search on this site

Search in forums

Home » U++ Library support » U++ Core » Capturing memory alloc problems in Release

Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend

Capturing memory alloc problems in Release [message #60934]

Fri, 11 October 2024 14:04

koldo
Messages: 3417
Registered: August 2008

Senior Veteran

Hi all

I wanted to ask you how to capture memory alloc problems in release mode.

Apart from this, I wanted to ask you for advice on how to capture as many of the errors as possible that cause the program to crash in release mode.

I would also like to know your opinion about the best way to save the user's steps, so that in case of a crash, the actions he/she did before can be saved. What would be the simplest way to make a log of the user's actions: clicking each button, clicking a tab, etc.?

Best regards
Iñaki

Report message to a moderator

Re: Capturing memory alloc problems in Release [message #60935 is a reply to message #60934]

Fri, 11 October 2024 15:19

Didier
Messages: 706
Registered: November 2008
Location: France

Contributor

Hello Koldo,

To help tracking crash problems on client site, you can force you're app to log the stacktrace in a file (or at least to stdout and laucnher a launcher script can then log it to a file)
This works fine in debug and release mode except that the stacktrace is not explicit in release mode.

To get better messages in release mode, you just need to activate debug info in release mode (it won't be as rich as in debug mode because of optimisations but it will bring you precious information Wink

)

Report message to a moderator

Previous Topic:	Compiler warning in Topt.h L177
Next Topic:	Is there a way to add checkboxes to a DropList?

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Sun Jan 19 05:05:42 CET 2025

Total time taken to generate the page: 0.02850 seconds