All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rahul Pande <rahul.pande@wipro.com>
To: MIPS <linux-mips@linux-mips.org>
Subject: pthread issues
Date: Fri, 25 Jul 2003 14:55:41 +0530	[thread overview]
Message-ID: <3F20F795.464D14EB@wipro.com> (raw)

Hi,

    I am trying to run a pthread based application on the AMD au1500
mips processor for linux version 2.4.21pre. The pthread_create function
does not return, i am attaching the strace of the process, where
pthread_create() is the call after the write statement "Creating a
thread". The thread seems to go into a sigsuspend mode after doing a
clone() and it never seems to return from there and so the thread
creation operation does not complete.

    Are there any patches that i need to apply or Are there any specific
define flags to be enabled for compilation. Please let me know if i can
run thread applications on mips.

Thanks and Regards,
          rahul





write(1, "Creating a thread\n", 18Creating a thread
)     = 18
getrlimit(RLIMIT_STACK, {rlim_cur=8192*1024, rlim_max=RLIM_INFINITY}) =
0
setrlimit(RLIMIT_STACK, {rlim_cur=2044*1024, rlim_max=RLIM_INFINITY}) =
0
brk(0x10003000)                         = 0x10003000
pipe([721840640, 4230684])              = 4
clone(child_stack=0x100027a8,
flags=CLONE_VM|CLONE_FS|CLONE_FILES|CLONE_SIGHAND)
 = 385
[pid   384] write(5, "\200\373\363*\5\0\0\0\0\0\0\0\377\377\377\377
y\377\177"..
., 148 <unfinished ...>
[pid   385] rt_sigprocmask(SIG_SETMASK, ~[TRAP 33],  <unfinished ...>
[pid   384] <... write resumed> )       = 148
[pid   385] <... rt_sigprocmask resumed> NULL, 16) = 0
[pid   384] rt_sigprocmask(SIG_SETMASK, NULL,  <unfinished ...>
[pid   385] read(4,  <unfinished ...>
[pid   384] <... rt_sigprocmask resumed> [32], 16) = 0
[pid   385] <... read resumed>
"\200\373\363*\5\0\0\0\0\0\0\0\377\377\377\377 y\
377\177"..., 148) = 148
[pid   384] write(5,
"\300\235\272*\0\0\0\0\0\0\0\0\244|\265*\260\345\300*\0"...
, 148 <unfinished ...>
[pid   385] poll( <unfinished ...>
[pid   384] <... write resumed> )       = 148
[pid   385] <... poll resumed> [{fd=4, events=POLLIN, revents=POLLIN}],
1, 2000)
 = 1
[pid   384] rt_sigprocmask(SIG_SETMASK, NULL,  <unfinished ...>
[pid   385] getppid( <unfinished ...>
[pid   384] <... rt_sigprocmask resumed> [32], 16) = 0
[pid   385] <... getppid resumed> )     = 384
[pid   384] sigsuspend(~[HUP INT QUIT TRAP IOT EMT FPE KILL SEGV USR1]
<unfinish
ed ...>
[pid   385] read(4,
"\300\235\272*\0\0\0\0\0\0\0\0\244|\265*\260\345\300*\0"...,
 148) = 148
[pid   385] old_mmap(0x7f600000, 2097152,
PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PR
IVATE|MAP_ANONYMOUS, -1, 0) = 0x7f600000
[pid   385] mprotect(0x7f600000, 4096, PROT_NONE) = 0
[pid   385] clone(child_stack=0x7f7ffbe0,
flags=CLONE_VM|CLONE_FS|CLONE_FILES|CL
ONE_SIGHAND|0x21) = 386
[pid   386] getpid()                    = 386
[pid   386] rt_sigprocmask(SIG_SETMASK, [32], NULL, 16) = 0
[pid   386] rt_sigprocmask(SIG_SETMASK, NULL, [32], 16) = 0
[pid   386] sigsuspend(~[HUP INT QUIT ILL IOT BUS SEGV TSTP] <unfinished
...>
[pid   385] kill(383, SIGRT_0)          = -1 ESRCH (No such process)
[pid   385] poll([{fd=4, events=POLLIN}], 1, 2000) = 0
[pid   385] getppid()                   = 384
[pid   385] poll( <unfinished ...>

                 reply	other threads:[~2003-07-25  9:30 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3F20F795.464D14EB@wipro.com \
    --to=rahul.pande@wipro.com \
    --cc=linux-mips@linux-mips.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.