From: Paul Hilfinger <hilfingr@EECS.Berkeley.EDU>
To: "Dykiel, Richard" <rdykiel@ntserver1.pacelinesystems.com>
Cc: "'gdb@sources.redhat.com'" <gdb@sources.redhat.com>
Subject: Re: sparc 32/64bit mixup?
Date: Mon, 07 May 2001 15:02:00 -0000 [thread overview]
Message-ID: <200105072202.PAA00850@tully.CS.Berkeley.EDU> (raw)
In-Reply-To: <596B27FF9CB1D411848000B0D07876E60DBE06@NTSERVER1>
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
>
>
prev parent reply other threads:[~2001-05-07 15:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-07 14:53 Dykiel, Richard
2001-05-07 15:02 ` Paul Hilfinger [this message]
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=200105072202.PAA00850@tully.CS.Berkeley.EDU \
--to=hilfingr@eecs.berkeley.edu \
--cc=gdb@sources.redhat.com \
--cc=rdykiel@ntserver1.pacelinesystems.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