crosutils: Use upstream dump_syms parameters for supporting splitdebug

cros_generate_breakpad_symbols

 #!/bin/bash
 # Copyright (c) 2010 The Chromium OS Authors. All rights reserved.
 # Use of this source code is governed by a BSD-style license that can be
 # found in the LICENSE file.
 
 # Script to generate minidump symbols in the format required by
 # minidump_stackwalk to dump stack information.
 #
 # NOTE: This script must be run from the chromeos build chroot environment.
 #
@@ skipping 59 matching lines @@
   fi
   return 0
 }
 
 # Dump given debug and text file.  Returns 1 if any errors, even
 # if they can be ignored, but only sets ANY_ERRORS if the error should not
 # be ignored (and we should not proceed to upload).
 function dump_file() {
   local debug_file="$1"
   local text_file="$2"
+  local debug_directory="$(dirname "${debug_file}")"
   # 64b ELF files may be installed on the target in PERL directories
   verify_not_64b_elf "${debug_file}" || return 1
   verify_not_64b_elf "${text_file}" || return 1
   # Dump symbols as root in order to read all files.
-  if ! sudo "${DUMP_SYMS}" "${debug_file}" "${text_file}" > "${SYM_FILE}" \
+  if ! sudo "${DUMP_SYMS}" "${text_file}" "${debug_directory}" > "${SYM_FILE}" \
        2> "${ERR_FILE}"; then
     # A lot of files (like kernel files) contain no debug information, do
     # not consider such occurrences as errors.
     if grep -q "file contains no debugging information" "${ERR_FILE}"; then
       warn "No symbols found for ${text_file}"
       return 1
     fi
     error "Unable to dump symbols for ${text_file}:"
     cat "${ERR_FILE}"
     ANY_ERRORS=1
@@ skipping 102 matching lines @@
     done
   fi
 
   info "Generated ${CUMULATIVE_SIZE}B of debug information"
 
   [ ${ANY_ERRORS} -ne 0 ] && die "Encountered problems"
   return 0
 }
 
 main "$@"