This is the mail archive of the libstdc++@gcc.gnu.org mailing list for the libstdc++ 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]

Re: [MIPS] libstdc++ test case problem with respect to try..throw and catch


On 3/2/07, Benjamin Kosnik <bkoz@redhat.com> wrote:

> i am getting failures with respect to try..throw..catch related test cases > > FAIL: 18_support/14026.cc execution test > FAIL: 19_diagnostics/stdexceptions.cc execution test > FAIL: 21_strings/basic_string/append/char/1.cc execution test > FAIL: 21_strings/basic_string/cons/char/1.cc execution test > FAIL: 21_strings/basic_string/cons/char/3.cc execution test > .... > ....

OK. This signals that something basic is wrong.

Have you run the g++ testsuite? You might want to start with fixing up
any issues in the compiler.

> I need help to debug this problem.
> where can i get the implementation details of try..throw and catch in
> gcc-3.4.4?

You'll find the C++ABI docs useful.

http://www.codesourcery.com/cxx-abi/

Most of the libsupc++ exception handling bits are in the libsupc++
directory. See the eh_* files.

Thanks for your reply,

I have debug the code for the throw exception in eh_throw.cc

and we have noticed that , In _Unwind_RaiseException (gcc/unwind.inc)
we are getting _URC_END_OF_STACK,so it is returning from there and
giving FAIL/ABORT.

In function uw_frame_state_for(),  unwind_Find_Fde() is not able to
find any frame descriptor element from the seen object or unseenobject
list.

Is ther any problem w.r.t stack frame initialization ?

-nidajm


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