OpenSolaris

1. Community: OS/Net (ON)
   1. Blogs
   2. Development Process
   3. Developer's Reference
      1. Introduction
      2. Prerequisites
      3. The Source Tree, part 1
      4. The Source Tree, part 2
      5. Building OpenSolaris
      6. Installing and Testing OpenSolaris
      7. Integration Procedure
      8. Best Practices and Requirements
      9. Glossary
   4. Discussions
   5. Installation (from source) Quickstart
      1. Annotated nightly(1) Mail Example
   6. Currently Known Issues
   7. CRT
      1. Advocates & Sponsors
      2. Becoming a CRT Advocate
      3. Charter
      4. RTI nits to avoid
      5. Sponsor Tasks
      6. Becoming a Sponsor
   8. Schedule
   9. ONNV Flag Days, Heads Ups, and Project Integration History
      1. All
      2. Builds 91-95
      3. Builds 86-90
      4. Builds 81-85
      5. Builds 76-80
      6. Builds 71-75
      7. Builds 66-70
      8. Builds 61-65
      9. Builds 56-60
      10. Builds 51-55
      11. Builds 46-50
      12. Builds 41-45
      13. Builds 36-40
      14. Builds 31-35
      15. Builds 26-30
      16. Builds 21-25
   10. Leaders
   11. Observers
   12. Putback Logs
   13. Developing Solaris
       1. Quality Death Spiral
   14. wx
   15. findunref and unreferenced files
   16. Bourne/Korn Shell Coding Conventions

Heads-up: bug 6408665 causes core dumps during build

Date: Tue, 4 Apr 2006 21:27:00 -0700
From: Bryan Cantrill <bmc at eng dot sun dot com>
To: on-all at sun dot com, onnv-gate at onnv dot eng dot sun dot com
Subject: Heads-up: bug 6408665 causes core dumps during build


All,

If you maintain a build machine, this mail is mandatory reading.

A bug that causes core dumps during a build -- bug 6408665 -- has been
introduced by the putback for the following bugs:

  6405927 USDT is-enabled probes
  6405929 USDT DOF with zero probes results in unsatisfiable memory allocation
  6405932 dead variables in usr/src/uts/common/dtrace/dtrace.c
  6405939 ::dofdump doesn't use section sizes correctly

This work was integrated on Thursday, March 30th and nightlies from March 31st
through April 4th (inclusive) have the bug.  The symptoms of the bug are
dtrace(1M) core dumping during the build process.  The core dumps will have
roughly the following signature:

  % pstack core.dtrace.347515
  core 'core.dtrace.347515' of 347515:    /usr/sbin/dtrace -G -32 -C -xlazyload -s ../port/threads/plockstat.d -
   c4f8380c dt_probe_define (8249b78, 82492b0, 824a46d, 0, 16d, 0) + 316
   c4f693c5 process_obj (8070a78, 804723a, 8046d40) + a73
   c4f697f5 dtrace_program_link (8070a78, 8074d80, 2, 8068b18, 16, 8068a7c) + 5b
   08052812 link_prog (8068b00) + e4
   080546a9 main     (1f, 8046efc, 8046f7c) + cd7
   08051972 ???????? (1f, 8047136, 804713d, 8047140, 8047144, 8047147)
 
I just integrated the fix for this; if you maintain a build machine, you will
want to _not_ BFU to bits that are dated later than 3/30 and before 4/5.
BFU'ing to bits dated on or later than 4/5 will (or should, anyway) yield a
clean build.

On behalf of Team DTrace, let me extend my apologies to those of you who
were inconvenienced by this -- and needless to say, we are modifying our
pre-integration testing to include a full build running on any DTrace
modifications!

	- Bryan

--------------------------------------------------------------------------
Bryan Cantrill, Solaris Kernel Development.       http://blogs.sun.com/bmc