c++ - using catch(...) (ellipsis) for post-mortem analysis -


Any other query otherwise hold unconnected to hold (...) main () <{code> try {} with hold (...) {} block It seems like an interesting idea that can save a lot of time in debugging the program and gives at least one indication of what happened.

The essence of the question is what information can be retrieved << and how to recover it (to access and identify whatever Was caught)

In addition to this, which warning is attached to it. Specifically:

  • Will it play well with threads that will rise later?
  • Will not break the handling of segfaults (taken as a sign elsewhere)
  • This does not affect other efforts ... assuming the expected exceptions Essentially catch nested blocks?

    • Yes, that's a good idea.

    If you give the main part to avoid the exception, then this implementation is defined, the stack is uninterrupted before the weather closes. So in my opinion it is important that you catch all the exceptions in the main.

    The question is, what to do with them.
    See some OS (MS and SE), provide some additional debugging features so that it is useful to throw the exception again (because the stack is still useless) after catching it. 

      int main (try /// all real code} // I see a little bit more in capturing other exceptions (// possibly better logging) if the exception is caught You may have gone / and it is decided that you should have done it here before. Grip (std :: exception const & amp; a) {// log e (...) A little better error message ... throwing; Hold (...) // Hold all the exceptions. Force the stack to open correctly {// You want to do something humble that is polite to throw; // throwing the exception again so that OS gives you the opportunity to debug

It should have no effect threads. Normally you have to manually join any child's thread to ensure that they have left. The exact description of what happens to the main exhaust, when the main performance is not well defined (thus read your documentation), but usually all child threads will die instantly (a dirty and terrible death which opens up their heap Not included).

If you are talking about exceptions in hair thread. Then it is not well defined (so read your document), but if a thread exits through an exception (i.e. used to start the exit of the thread due to an exception and not return) , Then it usually causes the application to end (similar effect as above). Therefore it is best to always stop the exception all from exiting the thread.

  • Will not break segfaults (captured anywhere in the form of a signal)

Signal exception handling Are not affected by the mechanism.
However, because the signal handler can have a strange structure on the stack (to get the normal code back for its own return) it is not a good idea to throw an exception inside the signal handler because it has unexpected results. (And certainly not portable)

  • Will not this affect other efforts ... The block is essentially nested inside, which are supposed to handle the expected exceptions?

There should be no effect on other handlers.


Comments

Post a Comment

Popular posts from this blog

sql - dynamically varied number of conditions in the 'where' statement using LINQ -

I am using my first project LINQ (in mvc), so maybe there's something very simple that I remember. However, a day of searching and experimenting does not work, so it works. I am trying to write a LINQ query (Linux to SQL) in which in many cases where the statement is different from an OR or an AND. We do not know how many conditions are going in the query till runtime. This search is for filter control, where the user can choose multiple criteria for filtering. Select from table where table.col = 1 or table.col = 2 or table.col = 7 .... 'Other number of conditions Before I just create the SQL query as a string, while looping over all the situations. However, it seems that there should be a good way to do this in LINQ. I tried to use Expression trees, but they had a second thought for this moment on my head, where the lambda function was to be executed inside the statement such as: values ​​for matchingRows = matchingRows for each value Where (function (row) row.c...
Read more

asp.net mvc - Dynamically Generated Ajax.BeginForm -

I have a problem with ASP.NET MVC Ajax forms. I generate many Ajax form in a table such as: & Lt; Input type = "submit" name = "activity" value = "add activity" / & gt; & Lt;%}% & gt; & Lt; / TD & gt; & Lt; / TR & gt; & Lt;%}% & gt; So far so good. When I post one of those forms, it gives a partial view in a div, and in this new partial view a new Ajax Beginnform (which is not in Genesis form) This second Ajax Beginnorf is exactly like the ones I got on the table, but when I post it, I do not get the "Ajax Post", but a normal post that sends me to a new page, I do not know whether the two Ajax forms What is the reason for the difference between, why is it the "dynamically generated" Ajax form behaves like a normal HTML form? By the way, I know that I can do it in different ways using javascript, but I would like to understand whether it can only be done using MVC helplars and Ajax lib...
Read more

Debug on symbian -

I am using trk for phone debug This works well for the Holorld project But when I start the project in phone debug mode 1) the load failed 2) TrkProtocolPlugin: to target the specified file Failure (please verify If any body understands what problem I am experiencing, then this problem helps me Pre-release If the application has the privileges assigned (with the appropriate certificate) itemprop = "text" > In your case, I will check: / li> If there is no conflict of application ID with any other application of device If there are problematic commands in the installation package (for example copy copy for non-accessible directories)
Read more