From: Joel Soete <soete.joel@tiscali.be>
To: John David Anglin <dave@hiauly1.hia.nrc.ca>
Cc: lamont@debian.org, parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] [gcc] should we teach gcc some new tricks?
Date: Thu, 05 May 2005 16:20:22 +0000 [thread overview]
Message-ID: <427A47C6.7060400@tiscali.be> (raw)
In-Reply-To: <200505022046.j42KkQnh000694@hiauly1.hia.nrc.ca>
Hello Dave,
Come back to expect pb:
o I just grab dpkg src and while I rebuild it localy I noticed that:
./configure [snip] --enable-threads
[snip]
checking for building with threads... configure: WARNING: Expect is not fully thread-enabled. Although significant work has been
done towards that goal, it is not complete. Continue compiling at your own risk.
no (default)
[snip]
? do you also used this '--enable-threads' options
o I also grab the latest 5.43.0 release and btw lfs recommended the patch: expect-5.43.0-spawn-1.patch
<http://lfs-matrix.net/lfs/view/development/chapter05/expect.html>
? do you already test it?
Thanks,
Joel
John David Anglin wrote:
>>>> IAOQ[0]: sys_poll+0x274/0x298
>>>> IAOQ[1]: sys_poll+0x278/0x298
>>>> RP(r2): sys_poll+0x17c/0x298
>>>>
>>>> # disasm 0ed5d240
>>>> 0: 0e d5 d2 40 sth r21,0(sr3,r22)
>>>
>>>Where did this address come from? IAOQ[0] = 0x101b22e4.
>>
>>Sorry, this is the faulting instruction. However, this isn't much help.
>>This isn't GCC code (GCC doesn't generate code using sr3). It's part of
>>a syscall asm. The value in sr3 seems wierd.
>
>
> The problem code is in fs/select.c:
>
> for (j=0; j < walk->len; j++, ufds++) {
> if(__put_user(fds[j].revents, &ufds->revents))
> goto out_fds;
> }
>
> The sth is in the __put_user code.
>
> Dave
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
next prev parent reply other threads:[~2005-05-05 16:20 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-24 13:07 [parisc-linux] [gcc] should we teach gcc some new tricks? Randolph Chung
2005-03-24 13:27 ` James A. Morrison
2005-03-24 16:19 ` John David Anglin
2005-03-24 16:59 ` Grant Grundler
2005-03-24 17:35 ` John David Anglin
2005-03-24 21:23 ` Grant Grundler
[not found] ` <200503242133.j2OLXl4R020985@hiauly1.hia.nrc.ca>
2005-03-24 22:33 ` Grant Grundler
2005-03-24 23:34 ` John David Anglin
2005-03-24 23:55 ` Randolph Chung
2005-03-24 23:59 ` Randolph Chung
2005-03-25 0:07 ` John David Anglin
2005-06-22 19:54 ` Joel Soete
2005-06-23 3:23 ` John David Anglin
2005-06-23 5:27 ` Grant Grundler
2005-06-23 6:10 ` Joel Soete
2005-03-24 19:37 ` James A. Morrison
2005-03-24 21:33 ` Grant Grundler
2005-03-26 8:55 ` Matthias Klose
2005-03-26 15:48 ` John David Anglin
2005-03-26 21:35 ` Grant Grundler
[not found] ` <16971.44399.144991.110733@gargle.gargle.HOWL>
2005-03-29 1:36 ` John David Anglin
2005-03-31 12:08 ` Michael S. Zick
2005-05-02 18:37 ` Joel Soete
2005-05-02 19:01 ` John David Anglin
2005-05-02 20:20 ` John David Anglin
2005-05-02 20:46 ` John David Anglin
2005-05-05 16:20 ` Joel Soete [this message]
2005-05-05 17:07 ` John David Anglin
2005-05-05 18:41 ` Joel Soete
[not found] <200505031334.j43DYRBT004104@hiauly1.hia.nrc.ca>
2005-05-03 17:58 ` Joel Soete
2005-05-03 19:00 ` John David Anglin
-- strict thread matches above, loose matches on Subject: below --
2005-06-23 7:19 Joel Soete
2005-06-23 13:09 ` John David Anglin
[not found] <42B91C1400000F85@mail-1-bnl.tiscali.it>
2005-06-25 6:46 ` John David Anglin
2005-06-25 8:29 ` Joel Soete
2005-07-01 13:43 ` Joel Soete
[not found] <42C81991.6030502@tiscali.be>
2005-07-03 18:47 ` John David Anglin
2005-07-04 14:51 ` Joel Soete
2005-07-05 14:59 ` Joel Soete
2005-07-07 1:27 ` John David Anglin
[not found] <200507051816.j65IGuIY028621@hiauly1.hia.nrc.ca>
2005-07-06 16:40 ` Joel Soete
2005-07-06 17:00 ` John David Anglin
[not found] <42B91C1400005075@mail-1-bnl.tiscali.it>
2005-07-09 15:42 ` Joel Soete
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=427A47C6.7060400@tiscali.be \
--to=soete.joel@tiscali.be \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=lamont@debian.org \
--cc=parisc-linux@lists.parisc-linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox