From: Doug Evans <dje@transmeta.com>
To: Bob Rossi <bob@brasko.net>
Cc: gdb@sources.redhat.com
Subject: Re: cvs update
Date: Thu, 07 Aug 2003 16:08:00 -0000 [thread overview]
Message-ID: <16178.31080.182197.255405@casey.transmeta.com> (raw)
In-Reply-To: <20030807152546.GA21305@white>
Bob Rossi writes:
> It also seems
> like you are saying to *not* just update the gdb tree. I have to update
> everything it depends on?
That's a judgement call.
[pedantic: it's based on one's experience, what one is
currently working on, how many trees one has checked out, which
modules are in each tree, knowledge of changes that have gone in since
the last update, knowledge of what versions of installed tools
are in use, and I'm guessing various other things I'm forgetting.]
For the context of being fairly new to gdb, with just the
gdb module checked out, I would update everything in the gdb module
every time (using the way I previously showed).
[pedantic: even that could get one into trouble. As Michael points out,
various changes in other tools can cause problems. If you're
on a fairly old linux system, for example, with a fairly old
binutils, for example, and you need support for something that's
only recently been fixed, you may find you have to either install
newer versions of those tools or start using a combined tree.
But if you're fairly new, I wouldn't worry about it at all. TMI.
Just file this away for future reference.]
> I am new at working with gdb, sorry for the low level questions.
No problem.
next prev parent reply other threads:[~2003-08-07 16:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-07 11:32 Bob Rossi
2003-08-07 15:08 ` Doug Evans
2003-08-07 15:22 ` Doug Evans
2003-08-07 15:26 ` Bob Rossi
2003-08-07 16:08 ` Doug Evans [this message]
2003-08-07 15:36 ` David Carlton
2003-08-07 15:50 Michael Elizabeth Chastain
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=16178.31080.182197.255405@casey.transmeta.com \
--to=dje@transmeta.com \
--cc=bob@brasko.net \
--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