test

test

[Wayne Ho]

test message send from Yahoo


_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com

test

[demo, newater]

test

[argencorreo]

test

[argencorreo1]

test

[a_golzalmo]

test

[a_golzalmo_]

test

test

[a_golzalmo_]

test

test

[a_golzalmo_]

test
4yonv01.jpg

test

[Charles Wilkins]

test

Re: test

[Scott Bronson]

I think so, but I haven't seen the message I sent two days ago...

	- Scott

>
On Fri, Mar 23, 2001 at 11:33:36AM -0500, Christopher Faylor wrote:
> Is this group on?
> 
> cgf
> 
From fnasser@cygnus.com Fri Mar 23 10:37:00 2001
From: Fernando Nasser <fnasser@cygnus.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: GDB Discussion <gdb@sources.redhat.com>
Subject: Re: TODO vs bug data base
Date: Fri, 23 Mar 2001 10:37:00 -0000
Message-id: <3ABB97EA.44F7C8A2@cygnus.com>
References: <3ABA1637.18A2EE1C@cygnus.com>
X-SW-Source: 2001-03/msg00257.html
Content-length: 345

Andrew Cagney wrote:
> 
> As a corollary, should ``Fix:'' generally be reserved for ``fixes'' -
> i.e. patches (Show me the money^D^D^D patch :-).
> 

Yes, that what "Fix:" was meant for, I believe.

-- 
Fernando Nasser
Red Hat - Toronto                       E-Mail:  fnasser@redhat.com
2323 Yonge Street, Suite #300
Toronto, Ontario   M4P 2C9
From tanvir.hassan@tumisoftware.com Fri Mar 23 14:30:00 2001
From: Tanvir Hassan <tanvir.hassan@tumisoftware.com>
To: 'Michael Elizabeth Chastain' <chastain@cygnus.com>, gdb@sourceware.cygnus.com, Tanvir Hassan <tanvir.hassan@tumisoftware.com>
Subject: RE: using GDB 5 on Solaris 7 with Sun WS5.0
Date: Fri, 23 Mar 2001 14:30:00 -0000
Message-id: <3DD49A5C2322D411B6AE00C00D01611506CD80@HELIOS>
X-SW-Source: 2001-03/msg00258.html
Content-length: 3334

Here's the stuff I get from "man CC" on SunWorkshop 5 C++:

Note that -compat=5 (which lets me use STL) will set the __cplusplus macro
to "199711L".  I don't know if that helps in determining which ABI those
guys are following.  Also, I tried to compile helloworld.cpp with -g and see
if the newest snapshot (23/Mar/2001) could debug it without me resorting to
-xs and it cannot.  Is there an option or config.h option that I need to
enable psymtab stuff?


     -compat[=(4|5)]
               Sets the compiler to be compatible with 4.0.1,
               4.1, and 4.2 compilers; or with full 5.0. This
               option controls the preprocessor __cplusplus
               macro.

               The C++ compiler has two principal modes.  One
               accepts the semantics and language defined by the
               Annotated C++ Reference Manual (ARM) and used in
               the 4.2 compiler (the compatibility mode, -com-
               pat=4).  The other accepts constructs according to
               the ANSI/ISO standard (standards mode, -compat=5).
               These two modes are incompatible with each other
               because the ANSI/ISO standard forces significant,
               incompatible changes in name mangling, vtable lay-
               out, and other ABI details. These two modes are
               differentiated by the -compat option as shown in
               the following values.

               Value          Meaning

               -compat=4      Compile for compatibility with C++
                              4.0.1, C++ 4.1, and C++ 4.2 (Sets
                              __cplusplus macro to 1.)

               -compat=5      Compile with full C++ 5.0 features.
                              (Sets __cplusplus macro to
                              199711L.)

               Defaults:

               If the -compat option is not specified, -compat=5
               is assumed.  If only -compat is specified, -com-
               pat=4 is assumed.

               Interactions:

               The -xarch=v9 option and the -compat[=4] option
               are not supported when used together.

-----Original Message-----
From: Michael Elizabeth Chastain [ mailto:chastain@cygnus.com ]
Sent: Friday, March 23, 2001 9:23 AM
To: gdb@sourceware.cygnus.com; tanvir.hassan@tumisoftware.com
Subject: Re: using GDB 5 on Solaris 7 with Sun WS5.0


Hi Tanvir,

> I have heard that someone might have changed GDB to do "lazy" loading
> of symbols by reading them from the *.o instead of the exe and thus
> obviating the need for "-xs", but I don't see any mention of this in
> any of the source.

That is the "partial symtab" (psymtab) code.

> 2) the name mangling/vtable scheme of Sun WS5.0 is apparently using the
> ISO/ANSI ABI standard and GDB cannot deal with it (it needs an new BFD to
> handle this?  or is there a generic name de-mangling place in the code?)

Recent snapshots of gdb, and the current CVS version of gdb, operate with
the new multi-vendor C++ ABI:

  http://reality.sgi.com/dehnert_engr/cxx/cxx-summary.html

If you could provide a URL or an ISO reference number for that "ISO/ANSI
ABI standard", I could check if it's the same as the "new ABI" standard
that we're working on supporting.

Michael Elizabeth Chastain
<chastain@redhat.com>
"love without fear"
From dan@www.cgsoftware.com Fri Mar 23 14:35:00 2001
From: Daniel Berlin <dan@www.cgsoftware.com>
To: Tanvir Hassan <tanvir.hassan@tumisoftware.com>
Cc: "'Michael Elizabeth Chastain'" <chastain@cygnus.com>, gdb@sourceware.cygnus.com
Subject: RE: using GDB 5 on Solaris 7 with Sun WS5.0
Date: Fri, 23 Mar 2001 14:35:00 -0000
Message-id: <Pine.LNX.4.10.10103231734060.2353-100000@www.cgsoftware.com>
References: <3DD49A5C2322D411B6AE00C00D01611506CD80@HELIOS>
X-SW-Source: 2001-03/msg00259.html
Content-length: 3822

On Fri, 23 Mar 2001, Tanvir Hassan wrote:

> Here's the stuff I get from "man CC" on SunWorkshop 5 C++:
> 
> Note that -compat=5 (which lets me use STL) will set the __cplusplus macro
> to "199711L".  I don't know if that helps in determining which ABI those
> guys are following.  Also, I tried to compile helloworld.cpp with -g and see
> if the newest snapshot (23/Mar/2001) could debug it without me resorting to
> -xs and it cannot.  Is there an option or config.h option that I need to
> enable psymtab stuff?
Nope.
It's automagic.

> 
> 
>      -compat[=(4|5)]
>                Sets the compiler to be compatible with 4.0.1,
>                4.1, and 4.2 compilers; or with full 5.0. This
>                option controls the preprocessor __cplusplus
>                macro.
> 
>                The C++ compiler has two principal modes.  One
>                accepts the semantics and language defined by the
>                Annotated C++ Reference Manual (ARM) and used in
>                the 4.2 compiler (the compatibility mode, -com-
>                pat=4).  The other accepts constructs according to
>                the ANSI/ISO standard (standards mode, -compat=5).
>                These two modes are incompatible with each other
>                because the ANSI/ISO standard forces significant,
>                incompatible changes in name mangling, vtable lay-
>                out, and other ABI details. These two modes are
>                differentiated by the -compat option as shown in
>                the following values.

You are misreading it. All this means is that they changed their ABI to be
able to support the ISO standard, not that they are using a standard ABI.
They are most certainly not.  We have 0 support for their ABI, so you
won't be able to debug in any useful way.

 > >                Value
Meaning > 
>                -compat=4      Compile for compatibility with C++
>                               4.0.1, C++ 4.1, and C++ 4.2 (Sets
>                               __cplusplus macro to 1.)
> 
>                -compat=5      Compile with full C++ 5.0 features.
>                               (Sets __cplusplus macro to
>                               199711L.)
> 
>                Defaults:
> 
>                If the -compat option is not specified, -compat=5
>                is assumed.  If only -compat is specified, -com-
>                pat=4 is assumed.
> 
>                Interactions:
> 
>                The -xarch=v9 option and the -compat[=4] option
>                are not supported when used together.
> 
> -----Original Message-----
> From: Michael Elizabeth Chastain [ mailto:chastain@cygnus.com ]
> Sent: Friday, March 23, 2001 9:23 AM
> To: gdb@sourceware.cygnus.com; tanvir.hassan@tumisoftware.com
> Subject: Re: using GDB 5 on Solaris 7 with Sun WS5.0
> 
> 
> Hi Tanvir,
> 
> > I have heard that someone might have changed GDB to do "lazy" loading
> > of symbols by reading them from the *.o instead of the exe and thus
> > obviating the need for "-xs", but I don't see any mention of this in
> > any of the source.
> 
> That is the "partial symtab" (psymtab) code.
> 
> > 2) the name mangling/vtable scheme of Sun WS5.0 is apparently using the
> > ISO/ANSI ABI standard and GDB cannot deal with it (it needs an new BFD to
> > handle this?  or is there a generic name de-mangling place in the code?)
> 
> Recent snapshots of gdb, and the current CVS version of gdb, operate with
> the new multi-vendor C++ ABI:
> 
>   http://reality.sgi.com/dehnert_engr/cxx/cxx-summary.html
> 
> If you could provide a URL or an ISO reference number for that "ISO/ANSI
> ABI standard", I could check if it's the same as the "new ABI" standard
> that we're working on supporting.
> 
> Michael Elizabeth Chastain
> <chastain@redhat.com>
> "love without fear"
> 

test

[Christopher Faylor]

Is this group on?

cgf
From jtc@redback.com Wed Mar 21 15:59:00 2001
From: jtc@redback.com (J.T. Conklin)
To: GDB Discussion <gdb@sources.redhat.com>
Subject: Re: OBSOLETE GDB m68k platforms
Date: Wed, 21 Mar 2001 15:59:00 -0000
Message-id: <5msnkeua35.fsf@jtc.redback.com>
References: <3AB03EF5.FBB5ACF8@cygnus.com>
X-SW-Source: 2001-03/msg00133.html
Content-length: 821

>>>>> "Andrew" == Andrew Cagney <ac131313@cygnus.com> writes:
Andrew> As part of GDB 5.1, the following m68k platforms have been identified
Andrew> as candidates for obsolescence:
Andrew>
Andrew> 	m68*-isi-*
Andrew> 	m68*-sony-*

We might also want to consider removing:
        m68*-rom68k-*
        m68*-*bug-*

They all build, in fact they are all aliases to the generic embedded
m68k target.  If I recall corectly, these targets exist because back
in the pre-libgloss BSP days, newlib contained code for eval boards
with these ROM monitors so an entire separate toolchain (including
compiler, binutils, gdb, etc.) was built when only a tiny bit of code
was different.  

These are other aliases that don't make sense today:
        m68*-monitor-*
        m68*-est-*

        --jtc

-- 
J.T. Conklin
RedBack Networks