Re: sparc 32/64bit mixup?

[Paul Hilfinger <hilfingr at EECS dot Berkeley dot EDU>]

Last time I checked, a 32-bit Sparc process could not successfully
'proc' a 64-bit Sparc process.

P. Hilfinger



 > Hello,
 > somebody's already got that kinf of error when running a program under gdb?
 > 
 > --------------------------------------------
 > rdykiel@sol1 [15]: gdb osedb
 > GNU gdb 5.0
 > Copyright 2000 Free Software Foundation, Inc.
 > GDB is free software, covered by the GNU General Public License, and you are
 > welcome to change it and/or distribute copies of it under certain
 > conditions.
 > Type "show copying" to see the conditions.
 > There is absolutely no warranty for GDB.  Type "show warranty" for details.
 > This GDB was configured as "sparc-sun-solaris2.7"...
 > (gdb) b main
 > Breakpoint 1 at 0x28c2c: file ../example/db.c, line 154.(gdb) r
 > Starting program: /export/home2/rdykiel/build/osedb/obj/solaris/osedb 
 > procfs: init_inferior, get_traced_signals line 4565, /proc/6601: Value too
 > large for defined data type.
 > -----------------------------------------------
 > 
 > The problem occurs on a 32bit sparc running solaris2.7.
 > The SHELL environment variable points to a 64bit tcsh executable; this shell
 > is forked by gdb to run the debugged program. A truss of the run sequence
 > shows that gdb encounters an error Err#79 EOVERFLOW when reading the /proc
 > files of the tcsh process it created.
 > 
 > I'd like to know if it's a bug in gdb or an error in the configuration when
 > building gdb.
 > thanks
 > 
 > 
 > Richard Dykiel               (978) 250-7491
 > Paceline Systems Corp.
 > 9B Kidder Road
 > Chelmsford MA 01824
 > 
 >