Feature Requests
Search the entire project
This project's trackers
This project's forums
This project's tasks
This project's releases
This project's documents
This project's news
Project
People
Skill
Advanced search
Log In
|
New Account
Home
My Page
Projects
Code Snippets
Project Openings
PostgreSQL Build Farm
Summary
Activity
Forums
Tracker
Lists
Tasks
Docs
Surveys
News
SCM
Files
[#1000139] stacktrace from core dumps
View Trackers
|
Feature Requests
|
Download .csv
|
Monitor
Date:
2004-10-28 03:47
Priority:
3
State:
Open
Submitted by:
Kris Jurka (
jurka
)
Assigned to:
Andrew Dunstan (andrewd)
Category:
Group:
Summary:
stacktrace from core dumps
Detailed description
To debug server crashes it's necessary to have a backtrace from server crashes. I don't know how easy this is with various debuggers, but if the goal is to allow any developer to check the buildfarm for problems it's necessary.
Followup
Message
Date: 2006-07-14 12:55
Sender: Nobody
Note that on linux this may be as easy as prefixing "catchsegv" to the starting of the server. It installs a signal handler for SIGSEGV and prints a backtrace when it happens.
Date: 2004-10-28 13:12
Sender:
Andrew Dunstan
Logged In: YES user_id=104
The buildfarm is designed more as a monitoring device than a debugging device.
I don't typically do a lot with debuggers, so I might be barking up the wrong tree, but ISTM that this would be highly platform-specific. You would have to build with debug symbols turned on, which I think is the default, and then know where to find the relevant core file, and the debugger command to extract the stack trace. The last item could go in the config file I guess.
This seems like a nice idea but it's not at the top of my priority list.
Attached Files:
Changes:
Field
Old Value
Date
By
assigned_to
none
2005-07-14 12:55
andrewd