This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB 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: Regression: [Re: RFC: change "program exited" message]


> While the .exp testfile does not have too straightforward way to accept the
> non-zero exit code I do not think a testfile should return with exit code
> non-zero.  But I failed to modify the .adb file such way, isn't there some
> easy way, Joel?

The non-zero status code is a consequence of a feature that I am
testing in this testcase, which is an *unhandled* exception. So
I need the exception to propagate all the way.

So, I think we have no choice but to change the testcase itself,
or enhance gdb_continue_to_end to be able to say that we expect
the inferior to terminate with a non-zero status.

I think the latter solution is probably preferable, because I'm
pretty sure I'll mis-handle bareboard, or remote/gdbserver, or
some other unusual configuration...

I can look at that tomorrow.

-- 
Joel


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