[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[libunwind] RE: BACKTRACE for coredump in signal handler does come prope
From: |
Kotian, Deepak |
Subject: |
[libunwind] RE: BACKTRACE for coredump in signal handler does come proper for IA-64. |
Date: |
Wed, 24 Mar 2004 10:19:40 +0530 |
Alright, David. Thanks for the information.
Thanks and Regards
Deepak
-----Original Message-----
From: David Mosberger [mailto:address@hidden
Sent: Wednesday, March 24, 2004 3:43 AM
To: Kotian, Deepak
Cc: address@hidden; address@hidden
Subject: RE: BACKTRACE for coredump in signal handler does come proper
for IA-64.
>>>>> On Sat, 20 Mar 2004 12:43:32 +0530, "Kotian, Deepak" <address@hidden>
>>>>> said:
Deepak> Is there a reference document for this special handling or
Deepak> which section of the IA-64 document should be refered to get
Deepak> this information.
I'm not aware of a single document that discusses this in particular.
A general description of how signal handlers work can be found in any
(reasonable) Linux kernel book (including the one by yours truly).
The getunwind() system call and the DSO-approach are probably not very
well documented at the moment (the former was a stop-gap solution and
the latter is still quite new in glibc and, AFAIK, not fully
documented yet). But in any case, applications shouldn't have to
worry about these details when using a proper API, which in the case
of Linux, is libunwind.
--david