Search Results

Search found 3 results on 1 pages for 'user303967'.

Page 1/1 | 1 

• Any porting available of backtrace for uclibc?

  - by user303967

  We are running the uclibc linux on ARM 9. The problem is uclibc doesn't support backtrace. When a core dump happens, I cannot grab the call stack. Does anyone have a good solution for that? For example, an existing porting of backtrace for uclibc, or any good method to grab the call stack when a core dump happens (uclibc+ARM+Linux)?

  Read the article

• handle SIGSEGV in Linux?

  - by user303967

  Hi all, I need handle the SIGSEGV in my Linux app. The reason is some clean up(3-partry lib) must be done before generate core-dump. What is more, the clean up must be performed in the context of calling thread, cannot do in signal handler. So I plan in signal handler to pass the control to the calling thread, after the clean up finished, then use raise(SIGSEGV) to generate the core-dump. The real problem seems the signal_handler cannot pass the control to calling thread, no matter I use post_sem or some others. Any idea to handle this case? Possbile to hijack the SIGSEGV, then in SIGSEGV hander return to another thread to perform some clean up? signal(SIGSEGV, signal_handler); signal_handler() { ... post_sem(); ... } calling thread() { wait_sem(); clean_up(); ... }

  Read the article

• Any porting avaiable of backtrace for uclibc?

  - by user303967

  We are running the uclibc linux on ARM 9. The problem is uclibc doesn't support backtrace. When core-dump happen, cannot grap the call stack. Anyone has good solution on that? For example, an existing porting of backtrace for uclibc? or any good method to grap call stack when call dump happen(uclibc+ARM+Linux)? thanks

  Read the article

1