From: Russ Allbery <rra@stanford.edu>
To: gdb@sourceware.cygnus.com
Subject: Re: cvsup & sourceware repositories?
Date: Sat, 01 Apr 2000 00:00:00 -0000 [thread overview]
Message-ID: <yld7ous9w5.fsf@windlord.stanford.edu> (raw)
In-Reply-To: <bln3iig8e.fsf@rtl.cygnus.com>
Jim Kingdon <kingdon@redhat.com> writes:
> I don't really know cvsup well enough to know just how it compares, but
> we do have anonymous rsync of the CVS repository - see
> http://sourceware.cygnus.com/sourceware/ for details.
It's roughly equivalent. CVSup may send less information (and hence be
more efficient) than rsync since it understands CVS repository structure,
and it produces slightly nicer diagnostic output, but for the most part
either are as good.
--
Russ Allbery (rra@stanford.edu) < http://www.eyrie.org/~eagle/ >
From dan@cgsoftware.com Sat Apr 01 00:00:00 2000
From: Daniel Berlin <dan@cgsoftware.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: Richard Chan <cshihpin@dso.org.sg>, gdb@sourceware.cygnus.com
Subject: Re: GDB supporting namespace std?
Date: Sat, 01 Apr 2000 00:00:00 -0000
Message-id: <zot3k8pu.fsf@dan.resnet.rochester.edu>
References: <Pine.LNX.4.10.10001142208380.673-100000@cshihpin.dso.org.sg> <38A7E3AD.5BE72E9C@cygnus.com>
X-SW-Source: 2000-q1/msg00266.html
Content-length: 904
>>>>> "AC" == Andrew Cagney <ac131313@cygnus.com> writes:
AC> Chan Shih-Ping wrote:
>>
>> Does GDB support the use of namespace std::,
>> code compiled with -fhonor-std (and an
>> appropriately compiled libgcc.a) and using
>> std::string s.
>>
>> However attempts at using
>> print s.size
>>
>> gives messages like
>> Couldn't find method string::size()
AC> Given that no one has responded, I'd suspect the answer to be no.
AC> It sounds like a good problem to peruse.
Depends on how you look at it.
With DWARF2, and my overload resolution patch, this should work perfectly
fine.
With STABS, you need a patch i'm working on as we speak (It works, i'm just
trying to see if their is anything i'm missing).
Assuming mangling and everything is working fine, namespaces should have no
problem.
If they do, i'll make them have no problems.
:)
AC> Andrew
next prev parent reply other threads:[~2000-04-01 0:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-16 16:29 Jimmy Guo
2000-03-16 16:37 ` Jim Kingdon
2000-04-01 0:00 ` Russ Allbery [this message]
2000-04-01 0:00 ` Jimmy Guo
2000-04-01 0:00 ` Andrew Cagney
[not found] <Pine.LNX.4.10.10003161941510.6569-100000@hpcll168.cup.hp.com>
2000-03-16 19:03 ` Jimmy Guo
2000-03-16 22:45 Jimmy Guo
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=yld7ous9w5.fsf@windlord.stanford.edu \
--to=rra@stanford.edu \
--cc=gdb@sourceware.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