8 msgGetting process's memory usage
1 msglibgcc.mvars: No such file or directory
1 msgPlease Verify Your Email Address: REPLY to this...
2 msgGCC port for PICs
6 msgUnresolved symbol problem

Customizing uncaught exception messages
\ Yang Zhang (15 May 2008)
. \ me22 (15 May 2008)
. . \ Yang Zhang (15 May 2008)
. \ Joel Dice (15 May 2008)
. . \ Yang Zhang (15 May 2008)
. . . \ Ian Lance Taylor (15 May 2008)

1 msgListings for specialties such as: family practi...
1 msgMESSAGE NOT DELIVERED: photo Full for cole
2 msgatomic builtin routines
4 msgIs there a way to build a program without stdli...
3 msgOptimizer problem with repeated loops over memory
3 msgno include files in the resulting install of GC...
2 msgfar (48bit) pointer addressing
2 msgUsing libgcc library in commercial product
5 msgc++: Function style initializer
3 msgWarning
1 msgHelp needed building gcc-2.95.3 on HPUX 11.31 IA
13 msgProblem with FD_SET on mips
2 msgGCC and fdump-translation-unit
7 msgerror: missing terminating ' character while mo...
Subject:Customizing uncaught exception messages
Group:Gcc-help
From:Yang Zhang
Date:15 May 2008


Hi, is it possible to get more informative error messages for uncaught
exceptions? For instance, I'm interested in getting Java-like
tracebacks with file and line numbers. Currently what I see is far from
that, e.g.:

terminate called after throwing an instance of 'std::logic_error'
what(): basic_string::_S_construct NULL not valid

Is there any way to hook into the exception handling mechanisms and
produce such a traceback? If the solution is platform-dependent, I am
using GNU/Linux with gcc 4.2.3.

Thanks!
--
Yang Zhang
http://www.mit.edu/~y_z/


© 2004-2008 readlist.com