taskDDD - Tasks: task #8855, DDD log file should contain stack...

 
 

You are not allowed to post comments on this tracker with your current authentication level.

task #8855: DDD log file should contain stack dump

Submitter:  Peter Wainwright <pwainwright>
Submitted:  Wed 19 Nov 2008 06:47:44 PM UTC
   
 
Should Start On:  Tue 13 Jan 2009 12:00:00 AM UTC Should be Finished on:  Tue 13 Jan 2009 12:00:00 AM UTC
Category:  None Priority:  5 - Normal
Status:  None Privacy:  Public
Assigned to:  None Percent Complete:  100%
Open/Closed:  Closed Effort:  0.00

Tue 13 Jan 2009 08:33:50 PM UTC, comment #2: 

DDD already has the capacity to read its own core dumps.  However, this is broken by some modern Linux systems where the core file has a nonstandard name.

The fix for bug #24879 has been committed to Subversion trunk.

Peter Wainwright <pwainwright>
Wed 19 Nov 2008 06:47:44 PM UTC, comment #1: 

This item has been reassigned from the project DDD bugs tracker to your tracker.

The original report is still available at bugs #24879

Following are the information included in the original report:

[field #0]                  Item ID: 24879
[field #1]                 Group ID: 169
[field #2]              Open/Closed: Open
[field #3]                 Severity: 1 - Wish
[field #4]                  Privacy: Public
[field #9]                 Category: None
[field #10]             Submitted by: pwainwright
[field #11]              Assigned to: None
[field #12]             Submitted on: Wed 19 Nov 2008 18:35:01 GMT
[field #13]                  Summary: DDD log file should contain stack dump
[field #14]      Original Submission: When DDD receives a fatal signal, it should attempt to collect a decent stack dump and print it to the log file.

There are too many bug reports that end abruptly with "Segmentation fault". We need more information to fix the bugs. A stack dump would be a good start.

[field #16]               Item Group: None
[field #17]                   Status: None
[field #18]        Component Version: None
[field #19]         Operating System: None
[field #20]          Reproducibility: None
[field #21]               Size (loc): None
[field #22]            Fixed Release: None
[field #23]          Planned Release: None
[field #24]                   Effort: 0.00
[field #28]                 Priority: 5 - Normal
[field #31]         Percent Complete: 0%
[field #33]                  Release: None
[field #58]     Custom Select Box #1: None
[field #59]     Custom Select Box #2: None
[field #60]     Custom Select Box #3: None
[field #61]     Custom Select Box #4: None
[field #62]     Custom Select Box #5: None
[field #63]     Custom Select Box #6: None
[field #64]     Custom Select Box #7: None
[field #65]     Custom Select Box #8: None
[field #66]     Custom Select Box #9: None
[field #67]    Custom Select Box #10: None

Peter Wainwright <pwainwright>
Wed 19 Nov 2008 06:47:44 PM UTC, original submission:  

When DDD receives a fatal signal, it should attempt to collect a decent stack dump and print it to the log file.

There are too many bug reports that end abruptly with "Segmentation fault". We need more information to fix the bugs. A stack dump would be a good start.

Peter Wainwright <pwainwright>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by pwainwright (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

     

    Follow 5 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2009-01-13 pwainwright Percent Complete0% 100%
        Open/ClosedOpen Closed
    2009-01-13 pwainwright Should Start On- 2009-01-13
        Should be Finished on- 2009-01-13
    2008-11-19 pwainwright Reassign itemDDD, bug #24879 DDD, task #8855

    Back to the top

    Powered by Savane 3.13-758e.
    Corresponding source code