Resending.  I sent this our yesterday afternoon, but I don't see it in 
mailfinder today.  Is there something wrong with the LSARC-ext at sun.com 
email alias?


Thanks,
George

George Vasick wrote:
> Rainer Orth wrote:
>> Raj Prakash <Raj.Prakash at sun.com> writes:
>>
>>> 2. Project Summary
>>>    2.1. Project Description:
>>>     Upgrade GDB from version 6.3 to 6.8, the latest released version.
>>>     Also, add support for debugging 64 bit executables.
>>>
>>> 4. Technical Description:
>>>     4.1. Details:
>>>     The GDB 6.8 source will be built both -m32 and -m64.  The 64 bit
>>>     build is required to support debugging of 64 bit executables.
>>>     Users running on 64 bit systems will get the 64 bit version of
>>>     GDB by default allowing them to debug both 32 bit and 64 bit
>>>     executables while users running on 32 bit systems will get the 32
>>>     bit version of GDB allowing them to debug 32 bit executables.
>>>     The isaexec command will be used to invoke the appropriate
>>>     version of the debugger depending on the system.
>>
>> Is there a reason to use isaexec on SPARC?  There's no 32-bit kernel
>> anymore, so the 32-bit binary will not be used by isaexec, but could only
>> invoked manually.  Unless the 64-bit GDB has trouble debugging 32-bit
>> programs, there's no reason to ship the 32-bit version on SPARC at all.
>> From the file listing below, it seems there is no /usr/bin/sparcv7/gdb*,
>> but this should be stated explicitly and the isaexec step omitted to 
>> avoid
>> the unnecessary overhead.
> 
> The thread "64-bit only projects?" was posted by Chris the day after I 
> filed this case.  It looks like the consensus is to put the 64 bit 
> binary directly into /usr/bin and eliminate isaexec for Sparc.  I'll 
> make the change.
> 
>>
>>>     4.5. Interfaces:
>>>     GDB 6.8 will be installed in /usr/bin with compatibility links
>>>     added to /usr/sfw/bin similar to the the current 6.3 version:
>>
>> I think those should be listed in this case as well.
> 
> Agreed.  I'll make the correction.
> 
>  > What about symlinks
>> for info and man pages?
> 
> The existing gdb 6.3 package does not include include man or info links 
> in sfw, only /usr/sfw/bin/gdb.  It is my understanding the sfw is 
> scheduled to go away at some point in the future.  Given that, I think 
> it does not make sense to add these links.
> 
>>
>>>     usr
>>>     usr/bin
>>>     usr/bin/amd64
>>>     usr/bin/amd64/gdb
>>>     usr/bin/amd64/gdbtui
>>>     usr/bin/gdb=../lib/isaexec
>>>     usr/bin/gdbtui=../lib/isaexec
>>>     usr/bin/i86
>>>     usr/bin/i86/gdb
>>>     usr/bin/i86/gdbtui
>>>     usr/bin/sparcv9
>>>     usr/bin/sparcv9/gdb
>>>     usr/bin/sparcv9/gdbtui
>>>     usr/sfw
>>>     usr/sfw/bin
>>>     usr/sfw/bin/gdb=../../bin/gdb
>>>     usr/sfw/bin/gdbtui=../../bin/gdbtui
>>>     usr/share
>>>     usr/share/info
>>>     usr/share/info/annotate.info
>>>     usr/share/info/gdb.info
>>>     usr/share/info/gdb.info-1
>>>     usr/share/info/gdb.info-2
>>>     usr/share/info/gdb.info-3
>>>     usr/share/info/gdb.info-4
>>>     usr/share/info/gdbint.info
>>>     usr/share/info/gdbint.info-1
>>>     usr/share/info/gdbint.info-2
>>>     usr/share/info/stabs.info
>>>     usr/share/man
>>>     usr/share/man/man1
>>>     usr/share/man/man1/gdb.1
>>>     usr/share/man/man1/gdbtui.1
>>
>> Rather than list all files and directories in SUNWgdb, it would be better
>> to list the exported (and imported) interfaces and their stability.
> 
> exported interfaces:
> * CLI commands: volatile
> * MI commands: volatile
> 
> imported interfaces:
> * ELF
> * DWARF
> * /proc
> * libdl.so.1
> * libcurses.so.1
> * libsocket.so.1
> * libnsl.so.1
> * libm.so.2
> * libexpat.so.1
> * libc.so.1
> * libmp.so.2
> * libmd.so.1
> * libscf.so.1
> * libuutil.so.1
> * libgen.so.1
> * libsmbios.so.1
> 
>  > In
>> particular, what about readline support?  Will it be included?
> 
> readline support is present.  gdb 6.8 includes its own copy of 
> readline-5.1 source which is used during the build.
> 
> 
> Thanks,
> George
> 
>>
>>     Rainer
>>

Reply via email to