Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The longjmp(3) man page on Unix says:</p> <blockquote> <p>The longjmp() routines may not be called after the routine which called the setjmp() routines returns</p> </blockquote> <p>I think it explains explains your concern that "<em>sometimes control never reachs BP1</em>". I don't think "<em>runs fine</em>" is reliable judgement. I'd rather expect it randomly runs fine and generally is messing up with stack.</p> <p>There are a few clear recommendations that should be taken into account while working mixing longjmp/setjmp with C++ exceptions in order to avoid crashes and undefined behaviour:</p> <ul> <li>Do not use setjmp/longjmp in C++ programs.</li> <li>If you use setjmp/longjmp functions in program where exceptions can occur, you are safe as long as they do not interact.</li> <li>Never longjmp in or out of try clause and catch clause.</li> <li>Never longjmp over point of initialization of automatic objects.</li> <li>Never longjmp pasy point of destruction automatic objects, especially if destructor is non-trivial.</li> <li>Never throw from signal handler.</li> <li>Never invoke longjmp from nested signal handler.</li> <li>Behaviour of longjmp from location X to location Y stays predictable and valid as long as if exception thrown at X and caught at X would have the same effect.</li> <li>If you mix setjmp/longjmp with exceptions, do not expect portability.</li> <li>Instead, refer to relevant details in documentation compiler you are using. For example, if you use Visual C++, read <a href="http://msdn.microsoft.com/en-us/library/yz2ez4as.aspx" rel="nofollow">Use setjmp/longjmp</a></li> </ul> <p>The question mentions dealing with legacy C code in programs written in C++. There has been an interesting discussion on sjlj issues in jpeg library during review of one of Boost libraries. The discussion was long but here is <a href="http://article.gmane.org/gmane.comp.lib.boost.devel/201425" rel="nofollow">essence with recommended options</a>.</p>
    singulars
    1. This table or related slice is empty.
    1. PODoes this code contain a hidden bug?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USmloskot
    1. USmloskot
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. CO`main()` hasn't returned at the time of the `longjmp()`
      singulars
      1. PO
      1. USfizzer
    2. COThanks ! But apart from point #1, I don't see where I missed the point (no pun intended).
      singulars
      1. PO
      1. USovercoder
    3. CO@overcoder Yes, that's correct. I wanted to cover some background information in my answer. Regarding MinGW, are you sure you're using MinGW with longjmp exceptions enabled? Run g++ -v to check it. I'm not MinGW user, but AFAIK MinGW distinguishes builds of C++ EH vs setjmp/longjmp. Note, MinGW-ready libraries like pthread offer separate builds for MingW (e.g. pthreadGCE.dll for C++ EH and pthreadGC.dll for sjlj EH). Simply these two gases don't mix.
      singulars
      1. PO
      1. USmloskot
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload