This is the mail archive of the gdb-patches@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [commit] Last major piece of fork tracing - vfork/exec


I hate to cause trouble here.  We're all on edge with the release
coming up (and this is also end-of-quarter for the red hat people).
But I have to speak up.

(I never no when EOQ is so thanks for the heads up).


The release is already being held up for the gdb.c++ -> gdb.cp
renaming.  The one-week comment period for that change ends this
afternoon.  Then I can commit this change to gdb HEAD.  Then it
needs a shakedown period in gdb HEAD.  Then I can commit the
change to gdb gdb_6_0-branch, and it will need a shakedown period
there as well.

The shake down will be telling people to do a cvs update -d src/gdb/testsuite/gdb.cp.


Andrew, I'm frankly amazed that you decided this feature was
release critical, but that's okay.  My role is to get it into
the branch expeditiously.

The release isn't been held up for the gdb.cp rename, it happened to slip nicely into the schedule. If it's not done by Sunday, I can easily do it myself. The bottom line is that if it screws up, and the testsuite is a brick, no one will notice. GDB on GNU/Linux will still work.


On the other hand, if vfork/exec breaks, GNU/Linux breaks and everyone notices.

Andrew



Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]