Re: [HACKERS] Stack trace
Yes, I use --enable-debug as an option in configure Regards, Bramandia R. On Mon, Nov 17, 2008 at 2:11 PM, Tom Lane [EMAIL PROTECTED] wrote: Bramandia Ramadhana [EMAIL PROTECTED] writes: Hm the backtrace() method does not give the line numbers of the methods in the stack trace, it only gives the hexadecimal offset. Is there anyway to retrieve the line numbers? Did you build with --enable-debug? regards, tom lane
Re: [HACKERS] Stack trace
On Mon, Nov 17, 2008 at 7:08 AM, Bramandia Ramadhana [EMAIL PROTECTED] wrote: Hm the backtrace() method does not give the line numbers of the methods in the stack trace, it only gives the hexadecimal offset. Is there anyway to retrieve the line numbers? the binutil addr2line should do the trick. Best, Hannes -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
Re: [HACKERS] Stack trace
Hm the backtrace() method does not give the line numbers of the methods in the stack trace, it only gives the hexadecimal offset. Is there anyway to retrieve the line numbers? I have tried to Google it but to no avail. Regards, Bramandia R. On Tue, Nov 4, 2008 at 12:26 PM, Emmanuel Cecchet [EMAIL PROTECTED]wrote: Bramandia Ramadhana wrote: Is there any way to print out the stack trace of the current location? Not sure if Postgres has something in the utils for that. You can use backtrace() in glibc. Solaris 9 libc has printstack(). Not sure what's available for Windows. I am looking for something like print_stack_trace(); that I can insert in arbitrary location in the code. Some references: http://www.tlug.org.za/wiki/index.php/Obtaining_a_stack_trace_in_C_upon_SIGSEGV http://www.delorie.com/gnu/docs/glibc/libc_665.html manu -- Emmanuel Cecchet FTO @ Frog Thinker Open Source Development Consulting -- Web: http://www.frogthinker.org email: [EMAIL PROTECTED] Skype: emmanuel_cecchet
Re: [HACKERS] Stack trace
Bramandia Ramadhana [EMAIL PROTECTED] writes: Hm the backtrace() method does not give the line numbers of the methods in the stack trace, it only gives the hexadecimal offset. Is there anyway to retrieve the line numbers? Did you build with --enable-debug? regards, tom lane -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
[HACKERS] Stack trace
Hi all, Is there any way to print out the stack trace of the current location? I am looking for something like print_stack_trace(); that I can insert in arbitrary location in the code. Thank you, Regards, Bramandia R.
Re: [HACKERS] Stack trace
Bramandia Ramadhana wrote: Is there any way to print out the stack trace of the current location? Not sure if Postgres has something in the utils for that. You can use backtrace() in glibc. Solaris 9 libc has printstack(). Not sure what's available for Windows. I am looking for something like print_stack_trace(); that I can insert in arbitrary location in the code. Some references: http://www.tlug.org.za/wiki/index.php/Obtaining_a_stack_trace_in_C_upon_SIGSEGV http://www.delorie.com/gnu/docs/glibc/libc_665.html manu -- Emmanuel Cecchet FTO @ Frog Thinker Open Source Development Consulting -- Web: http://www.frogthinker.org email: [EMAIL PROTECTED] Skype: emmanuel_cecchet -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
