404639 - core file detection must show stacks

Status: RESOLVED INACTIVE

(NSS :: Test, defect, P2)

Description

[Julien Pierre]

When programs crash during the QA in all.sh, core files are detected. But none of the content is displayed. Sometimes the trees get deleted too quickly in tinderbox and the nightly QA, so we never get a change to look at the cores. Given this, I think it would be useful to invoke a tool to display information automatically. For example, pstack can be called on a core file to display the stack on Solaris. I am not sure about other platforms. This should be done wherever possible.

Comment 1

[Slavomir Katuscak]

There is one bigger problem, most of machines are not configured to produce core file on failure. We need to enable it (ulimit -c) in testing script (all.sh, init.sh,...).

Comment 2

[Nelson Bolyard (seldom reads bugmail)]

Unsetting target milestone in unresolved bugs whose targets have passed.

Comment 3

[Julien Pierre]

Slavo,

This request is only asking that if your script detects a core file from one of our programs, you display its content, using pstack or any other tool appropriate for the platform. The machine configuration issues are independent of this.
This would be extremely useful, especially in tinderbox, where we can't easily access the build trees, and they get deleted quickly.

Comment 4

[BugBot [:suhaib / :marco/ :calixte]]

The bug assignee didn't login in Bugzilla in the last 7 months and this bug has priority 'P2'/severity 'major'.
:beurdouche, could you have a look please?
For more information, please visit auto_nag documentation.

Comment 5

[BugBot [:suhaib / :marco/ :calixte]]

In the process of migrating remaining bugs to the new severity system, the severity for this bug cannot be automatically determined. Please retriage this bug using the new severity system.