Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tristan Gingold <gingold@adacore.com>
To: gdb-patches@sourceware.org
Subject: [RFA] Fix Darwin failures on macscp.exp
Date: Wed, 03 Dec 2008 13:39:00 -0000	[thread overview]
Message-ID: <7D408FC4-C9AB-4EAF-A881-A30778266311@adacore.com> (raw)

Hi,

On Darwin the debugging info are never in the final executable.  They  
either stay in object files or
a separate debug file is created.
When an executable is directly created from source files (ie gcc -g -o  
x x.c), the separate debug file
is created (as the object files are temporary).  The Darwin tool that  
creates the separate debug file,
dsymutil, doesn't put .dwarf_macinfo into it.
As a consequence, there are a lot of failures in macscp.exp (more than  
100).

Instead of disabling this test on Darwin, I'd prefer to do a two steps  
compilation: first create an object
file and then link.

Tristan.

gdb/testsuite:
2008-12-03  Tristan Gingold  <gingold@adacore.com>

	* gdb.base/macscp.exp: Generate an object file during compilation
	to work around Darwin dsymutil limitations.

RCS file: /cvs/src/src/gdb/testsuite/gdb.base/macscp.exp,v
retrieving revision 1.15
diff -c -r1.15 macscp.exp
*** testsuite/gdb.base/macscp.exp	9 Oct 2008 16:49:47 -0000	1.15
--- testsuite/gdb.base/macscp.exp	3 Dec 2008 13:34:21 -0000
***************
*** 23,28 ****
--- 23,29 ----

   set srcfile macscp1.c
   set testfile "macscp"
+ set objfile "macscp.o"
   set binfile ${objdir}/${subdir}/${testfile}

   set options { debug }
***************
*** 32,38 ****
       lappend options additional_flags=-g3
   }

! if  {[gdb_compile "${srcdir}/${subdir}/macscp1.c" "${binfile}"  
executable $options] != "" } {
       untested macscp.exp
       return -1
   }
--- 33,41 ----
       lappend options additional_flags=-g3
   }

! if  {[gdb_compile "${srcdir}/${subdir}/macscp1.c" "${objfile}" \
! 	  object $options] != ""
!      || [gdb_compile "${objfile}" "${binfile}" executable $options] ! 
= "" } {
       untested macscp.exp
       return -1
   }


             reply	other threads:[~2008-12-03 13:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-03 13:39 Tristan Gingold [this message]
2008-12-04 13:16 ` Daniel Jacobowitz
2008-12-04 15:37   ` Tristan Gingold

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7D408FC4-C9AB-4EAF-A881-A30778266311@adacore.com \
    --to=gingold@adacore.com \
    --cc=gdb-patches@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox