From: Tom Tromey <tromey@redhat.com>
To: Geoffrey Keating <geoffk@cygnus.com>
Cc: gdb@sources.redhat.com
Subject: Re: missing construct_inferior_arguments
Date: Sat, 17 Nov 2001 14:50:00 -0000 [thread overview]
Message-ID: <87pu64jch5.fsf@creche.redhat.com> (raw)
In-Reply-To: Geoffrey Keating's message of "Tue, 27 Nov 2001 03:31:23 -0800"
>>>>> "Geoff" == Geoffrey Keating <geoffk@cygnus.com> writes:
Geoff> I'm having a problem that I think is related to your patch:
Geoff> 2001-11-21 Tom Tromey <tromey@redhat.com>
Geoff> Fix for PR gdb/209, PR gdb/156:
Geoff> * gdbarch.c, gdbarch.h: Rebuilt.
Geoff> * gdbarch.sh: Added `construct_inferior_arguments'.
Geoff> ..
Geoff> /home/geoffk/co/combined/gdb/gdbarch.c:509: undefined reference to
Geoff> `construct_inferior_arguments'
I checked in the fix for this last night.
Tom
WARNING: multiple messages have this Message-ID
From: Tom Tromey <tromey@redhat.com>
To: Geoffrey Keating <geoffk@cygnus.com>
Cc: gdb@sources.redhat.com
Subject: Re: missing construct_inferior_arguments
Date: Tue, 27 Nov 2001 10:25:00 -0000 [thread overview]
Message-ID: <87pu64jch5.fsf@creche.redhat.com> (raw)
Message-ID: <20011127102500.BR1q_CUXGnJvfmMTs67FVBHR7ICJSpqic5Jbok1Xpes@z> (raw)
In-Reply-To: <200111271131.fARBVNb24601@thief.cygnus.com>
>>>>> "Geoff" == Geoffrey Keating <geoffk@cygnus.com> writes:
Geoff> I'm having a problem that I think is related to your patch:
Geoff> 2001-11-21 Tom Tromey <tromey@redhat.com>
Geoff> Fix for PR gdb/209, PR gdb/156:
Geoff> * gdbarch.c, gdbarch.h: Rebuilt.
Geoff> * gdbarch.sh: Added `construct_inferior_arguments'.
Geoff> ..
Geoff> /home/geoffk/co/combined/gdb/gdbarch.c:509: undefined reference to
Geoff> `construct_inferior_arguments'
I checked in the fix for this last night.
Tom
next prev parent reply other threads:[~2001-11-27 18:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-16 14:58 Geoffrey Keating
2001-11-17 14:50 ` Tom Tromey [this message]
2001-11-27 10:25 ` Tom Tromey
2001-11-27 3:31 ` Geoffrey Keating
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=87pu64jch5.fsf@creche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=geoffk@cygnus.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