From: Jim Blandy <jimb@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: Alexander Larsson <alexl@redhat.com>, gdb@sources.redhat.com
Subject: Re: Final separate debug info patch
Date: Tue, 19 Nov 2002 03:53:00 -0000 [thread overview]
Message-ID: <vt265uthjus.fsf@zenia.red-bean.com> (raw)
In-Reply-To: <20021119053344.GA29601@nevyn.them.org>
Daniel Jacobowitz <drow@mvista.com> writes:
> On Tue, Nov 19, 2002 at 12:04:02AM -0500, Jim Blandy wrote:
> > There are some problems at the moment: DejaGNU has the name "unix"
> > hard-coded into it, and thinks that anything with another name is a
> > remote board. Some tests won't run if the target is remote. I think
> > I know how to persuade it that unix-separate-debug is still not a
> > remote target, but I'm just going to post this as is for the time
> > being.
>
> FYI, I do this. Here's how. This is a simple board description file
> which just uses a different C compiler, since GDB wasn't honoring CC:
>
> <quote>
> # The canonical unix board description.
> load_generic_config "unix";
>
> set_board_info compiler "gcc-3.2";
> set_board_info c++compiler "g++-3.2";
>
> global board
> proc ${board}_init { whole_name } {
> global board_info
> set board_info(unix3.2,isremote) 0;
> }
> </quote>
>
> Replace unix3.2 with whatever goes before the .exp. The ${board} bit
> is necessary and becomes something involving the local hostname, IIRC.
Okay --- that works. Here's the latest iteration:
---
load_base_board_description "unix"
set strip_to_file_program "/home/jimb/elfutils/bin/strip"
proc ${current_target_name}_compile {source dest type options} {
global strip_to_file_program
# Run the standard compilation procedure.
set result [default_target_compile $source $dest $type $options]
# If it didn't succeed, return directly.
if {[string compare $result ""] != 0} {
return $result
}
# Otherwise, strip the executable and copy its debug info to a
# separate file, leaving only a pointer behind.
if {[string compare $type executable] == 0} {
exec $strip_to_file_program -f ${dest}.separate-debug ${dest}
}
}
proc ${board}_init { whole_name } {
global board_info
set board_info(unix-separate-debug,isremote) 0
}
next prev parent reply other threads:[~2002-11-19 11:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-09 1:54 Alexander Larsson
2002-11-18 21:20 ` Jim Blandy
2002-11-18 21:32 ` Daniel Jacobowitz
2002-11-19 3:53 ` Jim Blandy [this message]
2002-11-18 23:47 ` Alexander Larsson
2002-11-19 3:38 ` Jim Blandy
2002-11-19 3:57 ` Alexander Larsson
2002-11-19 12:47 ` Alexander Larsson
2002-11-20 21:43 ` Jim Blandy
2002-11-20 23:35 ` Alexander Larsson
2002-11-19 5:00 ` Jim Blandy
2002-11-18 22:11 ` Jim Blandy
2002-11-18 23:51 ` Alexander Larsson
2002-11-19 0:02 ` Ulrich Drepper
2002-11-19 3:47 ` Jim Blandy
2002-11-19 3:53 ` Alexander Larsson
2002-11-19 4:38 ` Jim Blandy
2002-11-24 20:28 ` Jim Blandy
2002-11-25 5:37 ` Alexander Larsson
2002-11-25 9:44 ` Jim Blandy
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=vt265uthjus.fsf@zenia.red-bean.com \
--to=jimb@redhat.com \
--cc=alexl@redhat.com \
--cc=drow@mvista.com \
--cc=gdb@sources.redhat.com \
/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