From: Jim Blandy <jimb@zwingli.cygnus.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: kettenis@wins.uva.nl, gdb-patches@sourceware.cygnus.com
Subject: Re: RFA: minor watchpoint code cleanup
Date: Tue, 21 Mar 2000 15:33:00 -0000 [thread overview]
Message-ID: <npk8iv7vat.fsf@zwingli.cygnus.com> (raw)
In-Reply-To: <200003211817.NAA12429@indy.delorie.com>
> The reason is that IMHO we should avoid making a variable (`size')
> serve two puproses at the same time.
Good suggestion --- done.
I'm just waiting for Mark's approval.
From kettenis@wins.uva.nl Tue Mar 21 15:47:00 2000
From: Mark Kettenis <kettenis@wins.uva.nl>
To: jtc@redback.com
Cc: gdb-patches@sourceware.cygnus.com
Subject: Re: RFA: tm-nbsd.h: define IN_SOLIB_CALL_TRAMPOLINE
Date: Tue, 21 Mar 2000 15:47:00 -0000
Message-id: <200003212346.e2LNklX05555@delius.kettenis.local>
References: <5maejsgjl8.fsf@jtc.redbacknetworks.com>
X-SW-Source: 2000-03/msg00448.html
Content-length: 491
From: jtc@redback.com (J.T. Conklin)
Date: 21 Mar 2000 12:21:39 -0800
I submit the enclosed patch for approval. This allows programs linked
with shared libraries to be debugged on a.out-based NetBSD targets.
2000-03-21 J.T. Conklin <jtc@redback.com>
* tm-nbsd.h (IN_SOLIB_CALL_TRAMPOLINE): Define if not
SVR4_SHARED_LIBS.
Keeping in mind that one day we'll multi-arch the i386, wouldn't it be
better to have a function that does the trampoline detection?
Mark
From dan@cgsoftware.com Tue Mar 21 15:49:00 2000
From: Daniel Berlin <dan@cgsoftware.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: jtc@redback.com, gdb-patches@sourceware.cygnus.com
Subject: Re: RFA: i386/nbsd.mt, i386nbsd-nat.c
Date: Tue, 21 Mar 2000 15:49:00 -0000
Message-id: <Pine.LNX.4.10.10003211547370.15517-100000@propylaea.anduin.com>
References: <38D7F75F.522996A3@cygnus.com>
X-SW-Source: 2000-03/msg00449.html
Content-length: 975
Actually, i have patches to make FreeBSD build native just fine.
I merged the patches freebsd uses against 4.18 into the current gdb.
It fails some shared lib tests, but past that, it's fine.
I can submit them if you like.
On Wed, 22 Mar 2000, Andrew Cagney wrote:
> "J.T. Conklin" wrote:
> >
> > I submit the enclosed patch for approval. This change splits out
> > NetBSD native support from the FreeBSD, BSDI, and 386BSD support. The
> > changes I submitted earlier today convert the NetBSD target to use the
> > generic floating point register support, which conflicts with i386b-nat.c
> >
> > --jtc
> >
> > 2000-03-21 J.T. Conklin <jtc@redback.com>
> >
> > * i386/nbsd.mh (NATDEPFILES): Changed i386b-nat.c to i386nbsd-nat.c.
> > * i386nbsd-nat.c: New file.
>
> Ok. (The naming schema *-nat.c files is AWAL. Your consistent with
> other *bsd targets :-)
> Last time I tried FreeBSD couldn't build GDB native anyway.
>
> Andrew
>
next prev parent reply other threads:[~2000-03-21 15:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200003180006.TAA26919@zwingli.cygnus.com>
2000-03-19 1:45 ` Eli Zaretskii
[not found] ` <200003192255.e2JMtcs00643@delius.kettenis.local>
[not found] ` <200003200958.EAA09356@indy.delorie.com>
2000-04-01 0:00 ` Jim Blandy
[not found] ` <200003211817.NAA12429@indy.delorie.com>
2000-03-21 15:33 ` Jim Blandy [this message]
2000-04-01 0:00 ` Mark Kettenis
2000-03-21 15:57 ` Mark Kettenis
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=npk8iv7vat.fsf@zwingli.cygnus.com \
--to=jimb@zwingli.cygnus.com \
--cc=eliz@is.elta.co.il \
--cc=gdb-patches@sourceware.cygnus.com \
--cc=kettenis@wins.uva.nl \
/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