All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: gdb broken under linuxppc r5 tools
Date: Mon, 2 Aug 1999 11:50:34 -0400	[thread overview]
Message-ID: <19990802115034.A16484@them.org> (raw)
In-Reply-To: <99080211313600.00413@localhost.localdomain>; from kbhend on Mon, Aug 02, 1999 at 11:21:19AM -0400


On Mon, Aug 02, 1999 at 11:21:19AM -0400, kbhend wrote:
> 
> Hi Kevin,
> 
> > Kevin, Franz, et.al,
> > 
> > Earlier this year, Metrowerks and I signed the copyright assignments
> > required by the FSF.  Beginning August 9, I will be starting work at
> > Cygnus as a GDB engineer.  One of the things that I'll work on is a
> > merge of my patches into the current gdb mainline.  It'll be my goal
> > to get a solid, usable gdb up and running on Linux/PPC again.
> 
> Congrats!  It is good to hear from you again!  We still miss you on the LinuxPPC
> JDK porting team!  Care to rejoin?!? :-)
> 
> As for gdb, something changed seriously between Paul's 2.2.1 kernel running on
> a R4.1 build (gdb was very very stable when debugging shared libs) and Paul's
> 2.2.10 kernel running LinuxPPC R5 or YDL.

Could you possibly try booting 2.2.1 on this R5 or YDL system?  I'd
like to isolate this from kernel or userland problem.

Dan

/--------------------------------\  /--------------------------------\
|       Daniel Jacobowitz        |__|        SCS Class of 2002       |
|   Debian GNU/Linux Developer    __    Carnegie Mellon University   |
|         dan@debian.org         |  |       dmj+@andrew.cmu.edu      |
\--------------------------------/  \--------------------------------/

[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

  reply	other threads:[~1999-08-02 15:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-08-01 13:01 current recommended versions of glibc/egcs/binutils for R5? R Shapiro
1999-08-01 13:58 ` Franz Sirl
1999-08-01 18:38   ` gdb broken under linuxppc r5 tools Kevin B. Hendricks
1999-08-01 19:03     ` Franz Sirl
1999-08-01 20:12       ` kbhend
1999-08-01 20:24       ` Kevin Buettner
1999-08-01 20:54         ` Franz Sirl
1999-08-02 11:20         ` Gary Thomas
1999-08-02 15:21         ` kbhend
1999-08-02 15:50           ` Daniel Jacobowitz [this message]
1999-08-02 16:01         ` kbhend
1999-08-22 15:09   ` bug in glibc 2.1.2 new semaphore functions in libpthread? Kevin Hendricks
1999-08-24 21:09     ` Franz Sirl

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=19990802115034.A16484@them.org \
    --to=drow@false.org \
    --cc=linuxppc-dev@lists.linuxppc.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.