Use the existing PRINTPAGERANGE rather than allocating a new one....

printing/printing_context_win_unittest.cc

Index: printing/printing_context_win_unittest.cc
===================================================================
--- printing/printing_context_win_unittest.cc	(revision 70468)
+++ printing/printing_context_win_unittest.cc	(working copy)
@@ -1,4 +1,4 @@
-// Copyright (c) 2006-2008 The Chromium Authors. All rights reserved.
+// Copyright (c) 2011 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
@@ -38,7 +38,6 @@
   // Pretend the page range is 1-5, but since lppd->Flags does not have
   // PD_SELECTION set, this really shouldn't matter.
   lppd->nPageRanges = 1;
-  lppd->lpPageRanges = new PRINTPAGERANGE[1];

[Lei Zhang, 2011/01/05 01:34:54]

This is not needed, since we only call PrintDlgExMock() in a test where
|max_pages| is set to a dummy value > 0. Thus |lppd->lpPageRanges| is valid
already.

   lppd->lpPageRanges[0].nFromPage = 1;
   lppd->lpPageRanges[0].nToPage = 5;