Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: drow@false.org
Cc: Stefano.Frullani@frumar.it, gdb@sources.redhat.com
Subject: Re: gdb procfs 64bit Solaris problem
Date: Thu, 21 Apr 2005 19:27:00 -0000	[thread overview]
Message-ID: <200504211926.j3LJQfRk001359@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <20050421143457.GA890@nevyn.them.org> (message from Daniel Jacobowitz on Thu, 21 Apr 2005 10:34:57 -0400)

   Date: Thu, 21 Apr 2005 10:34:57 -0400
   From: Daniel Jacobowitz <drow@false.org>

   On Thu, Apr 21, 2005 at 04:31:03PM +0200, Stefano Frullani wrote:
   > 
   > > Did yoy compile gdb as a 64-bit executable?  To check run file(1) on
   > > your gdb executable.  If not please try reconfiguring and rebuilding
   > > gdb with the environment variable CC set to "gcc -m64".
   > >
   > > Mark

   Hi Mark,

   This seems to be an incredibly frequently recurring problem for
   sparc-solaris users.  Can we make GDB detect the problem?  I would
   suggest making configury default to 64-bit for sparcv9/sparc64, but
   that's not appropriate for gcc or binutils or other toplevel projects,
   probably.

That's seems like a good idea.  Have to think a bit though where to
stick this warning, but I'll find the proper spot.

Mark


  parent reply	other threads:[~2005-04-21 19:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-21 10:50 Stefano Frullani - NOSPAM
2005-04-21 12:37 ` M.M. Kettenis
2005-04-21 14:31   ` Stefano Frullani
2005-04-21 14:35     ` Daniel Jacobowitz
2005-04-21 14:41       ` Stefano Frullani - NOSPAM
2005-04-21 18:38       ` Eli Zaretskii
2005-04-21 19:27       ` Mark Kettenis [this message]
2005-04-21 19:28         ` Daniel Jacobowitz

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=200504211926.j3LJQfRk001359@elgar.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --cc=Stefano.Frullani@frumar.it \
    --cc=drow@false.org \
    --cc=gdb@sources.redhat.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