| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 3527.1 | why /exc on command line? | HNDYMN::MCCARTHY | A Quinn Martin Production | Fri Apr 04 1997 07:49 | 15 |
| Drew,
Compiling .0 without the /exc produces the expected results.
Adding:
- a call to cxx$set_condition(cxx_exception) causes the program to accvio
when the alarm goes off (I think this is expected since there is no
try/catch involved).
- a call to cxx$set_condition(unix_signal) causes the program to work
correctly.
Is there a reason they are using /except (ie is your simple program missing
what caused them to require it?)
Brian J.
|
| 3527.2 | | SPECXN::DERAMO | Dan D'Eramo | Fri Apr 04 1997 17:47 | 16 |
| >Adding:
> - a call to cxx$set_condition(cxx_exception) causes the program to accvio
> when the alarm goes off (I think this is expected since there is no
> try/catch involved).
It should cause the program to call terminate(), not to
accvio.
>Adding:
> - a call to cxx$set_condition(unix_signal) causes the program to work
> correctly.
That's interesting, as not calling cxx$set_condition at all
should be equivalent to calling cxx$set_condition(unix_signal).
Dan
|
| 3527.3 | | CSC32::D_SANFORD | | Fri Apr 04 1997 22:04 | 19 |
| It should work with /except right? They are using it because their
code also includes try / catch, the code they sent is just a
reduced version.
I suggested they try:
cxx$set_condition(unix_signal)
as a workaround. Hopefully this works... This customer was not
happy, logging every call <S1>, if this does not work I can expect
a call every hour until it is working. Was going to recommend he
downgrade to V5.2, but I held back.
I assume we might have two bugs here? Not defaulting to "unix_signal"
and alarm() not working with /except ?
Thank you for the quick response.
-drew
|
| 3527.4 | maybe just one but not two | HNDYMN::MCCARTHY | A Quinn Martin Production | Mon Apr 07 1997 08:37 | 21 |
| >> It should work with /except right? They are using it because their
I would think so. I'll have to check into this a little futher.
>> as a workaround. Hopefully this works... This customer was not
>> happy, logging every call <S1>, if this does not work I can expect
>> a call every hour until it is working. Was going to recommend he
>> downgrade to V5.2, but I held back.
Well let us know if it does not (I'm sure you will!).
>> I assume we might have two bugs here? Not defaulting to "unix_signal"
>> and alarm() not working with /except ?
Actually, in either case, I think we only have one problem and its
either that the default isn't occuring or that alarm() causes it to
fail.
Brian J.
|
| 3527.5 | cxxl$set_condition(unix_signal) worked | CSC32::D_SANFORD | | Wed Apr 09 1997 15:32 | 5 |
| Good news... the workaround appears to work! He asked when a
patch would be available, but I said since there is an easy
workaround it would only be fixed in a future release of C++.
-drew
|
| 3527.6 | still need to check it out | HNDYMN::MCCARTHY | A Quinn Martin Production | Wed Apr 09 1997 19:03 | 6 |
| >> patch would be available, but I said since there is an easy
>> workaround it would only be fixed in a future release of C++.
Gee - thanks !
bjm
|