This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libgcj/12740] Stack trace infrastructure improvements
- From: "aph at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 3 Nov 2003 11:50:17 -0000
- Subject: [Bug libgcj/12740] Stack trace infrastructure improvements
- References: <20031023033556.12740.bryce@mckinlay.net.nz>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12740
------- Additional Comments From aph at gcc dot gnu dot org 2003-11-03 11:50 -------
- libgcc's unwinder machinery should be used instead of backtrace()
This is probably true, but it may be slower.
- for security/classloader/accessibility checks, we should only walk the stack
as far as needed to complete the check, not the entire stack
I don't understand this. We don't walk the entire stack at the moment.