stack

Suppose I have something like this : try code_that_fails() catch _:_ -> ..... How do I print the stacktrace in the catch block? That block catches all exceptions, but I don't know how to print the stack... Can you help me? Christian From Erlang 21.0 onwards, there's a new official way to get the stack trace. An optional pattern match in the try expression on the third parameter in the exception, which will contain the stack trace: try code_that_fails() catch _:_:Stacktrace -> erlang:display(Stacktrace) end Older versions (OTP 20 and below) For versions of Erlang/OTP 20 and below, you need to

I have an activity with the translucent Theme : android:theme="@android:style/Theme.Translucent.NoTitleBar" Also the problem is reproduceable with just this Theme: <style name="MyTheme" parent="@android:style/Theme"> <item name="android:windowIsTranslucent">true</item> <item name="android:windowBackground">@android:color/transparent</item> <item name="android:colorBackground">@null</item> </style> This activity is loaded at startup and kept in memory (when I start this activity, I ad the FLAG_ACTIVITY_REORDER_TO_FRONT flag as extra). Problem : when I start this activity (from the menu), the

Suppose I have the following array: int list[3]={2,8,9}; printf("%p,%p,%p",(void*)&list[0],(void*)&list[1],(void*)&list[2]); Is it always guaranteed that &list[0]<&list[1]<&list[2] ? I had assumed it to be a hard and fast rule while using C, but now have to very sure about it as an OP just asked me about it when I answered his question about endianness Little endian or Big endian What gave me second thoughts is the stacks can grow up or down issue.I am not very sure about that so your rigorous answers are appreciated.Thanks. Yes, it's guaranteed that &list[0]<&list[1] and &list[1]<&list[2] .

I'm writing interrupt handling routines for x86_64. The ABI specifies that before calling a C function I must align the stack to 16 bytes. The x86_64 ISA specifies that on entry to an ISR, my stack is 8 byte aligned. I need to align my stack pointer to 16 bytes therefore. The issue is that on return from my C function, I must recover the (potentially) unaligned stack pointer so that I can return from my interrupt correctly. I wonder if there is a way to do this without using a general purpose register? Here's my solution to the question as put: pushq %rsp pushq (%rsp) andq $-0x10, %rsp call

I try to build an application which uses pthreads and __m128 SSE type. According to GCC manual, default stack alignment is 16 bytes. In order to use __m128, the requirement is the 16-byte alignment. My target CPU supports SSE. I use a GCC compiler which doesn't support runtime stack realignment (e.g. -mstackrealign). I cannot use any other GCC compiler version. My test application looks like: #include <xmmintrin.h> #include <pthread.h> void *f(void *x){ __m128 y; ... } int main(void){ pthread_t p; pthread_create(&p, NULL, f, NULL); } The application generates an exception and exits. After a

I want to finish all the activities which are running in the application means want to remove all the parent activities from stack. I want to implement logout functionality locally in my application so what I was thinking, I will finish all the activities started before and will start login activity again.. I should let you know this is not a recommended behavior in android since you should let itself to manage life circles of activities. However if you really need to do this, you can use FLAG_ACTIVITY_CLEAR_TOP I give you some sample code here, where MainActivity is the first activity in the