From: kbhend <kbhend@business.wm.edu>
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: gdb broken under linuxppc r5 tools
Date: Sun, 1 Aug 1999 16:12:32 -0400 [thread overview]
Message-ID: <99080116170800.00474@localhost.localdomain> (raw)
In-Reply-To: 99080121250000.02221@ns1102.munich.netsurf.de
On Sun, 01 Aug 1999, Franz Sirl wrote:
>
> Kevin, as a first measure, do you pass LD_BIND_NOW=1 in the environment?
>
> Franz.
Yes, that is the default we set with the jdk. Unfortunately it is no help.
Could this be kernel related? I saw this problem with some of Paul's kernels
under R4 and then all problems with gdb went away. Everything worked fine
under YDL but since my upgrade to LinuxPPC R5 and Paul's 2.2.10 kernel, the old
problems have re-appeared.
It is like some piece of cache is not being properly flushed.
By the way, I noticed from disassembling some code from egcs 1.1.2-12c that the
stwu instruction is being used again. I thought Gary Thomas patched the egcs
source to prevent stwu from being generated becuase of some serious problems
with it being used in certain combinations on 604e systems. Any info on this?
Thanks,
Kevin
[[ 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. ]]
next prev parent reply other threads:[~1999-08-01 20:12 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 [this message]
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
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=99080116170800.00474@localhost.localdomain \
--to=kbhend@business.wm.edu \
--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.