Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Eli Zaretskii" <eliz@gnu.org>
To: gdb@sources.redhat.com
Subject: Re: gdb procfs 64bit Solaris problem
Date: Thu, 21 Apr 2005 18:38:00 -0000	[thread overview]
Message-ID: <01c546a1$Blat.v2.4$333de320@zahav.net.il> (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>
> Cc: "M.M. Kettenis" <m.m.kettenis@alumnus.utwente.nl>,
> 	Stefano Frullani - NOSPAM <stefanodotfrullaniatfrumardotit@frumar.it>,
> 	gdb@sources.redhat.com
> 
> This seems to be an incredibly frequently recurring problem for
> sparc-solaris users.  Can we make GDB detect the problem?

I second the request.


  parent reply	other threads:[~2005-04-21 18:38 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 [this message]
2005-04-21 19:27       ` Mark Kettenis
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='01c546a1$Blat.v2.4$333de320@zahav.net.il' \
    --to=eliz@gnu.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