This is the mail archive of the gcc-help@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Exception Traceback / Frame Unwind


Dear gcc,

From a newbie, hope this hasn't been answered too many times in the past.

I see that gcc collects a frame unwind, either implicitly from the code or using the '-fexceptions'.

Our coding could benefit greatly from having access to this information. Specifically when running a daemon, to catch and report on these errors, complete with the frame unwind, yet continue to run as a daemon.

Can any member suggest a way of pro grammatically accessing the frame unwind information, without exiting the code?

Regards,

Ben Clewett.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]