public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] pthread lib setting for ia64?
Date: Sat, 01 Dec 2001 18:36:51 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590698805567@msgid-missing> (raw)

"Pereira, D LailaX E" <d.lailax.e.pereira@intel.com> writes:

|> Hi 
|> While running my program on a Linux machine (turbo linux) Itanium processor,
|> the program does a segmentation fault on a pthread_create(..) command. I
|> checked the arguments of the pthread_create(...) and there is no problem
|> with them. So I ran the program thru gdb , and got the following on seg
|> fault:
|> 
|> Starting
|> program:
|> /fxsvrux001/home1/depereir/Tmk_SMP-26/apps/test_C/bin.ia64_linux2/stress.udp
|> -- -n2 -N1 -hcopilot{,} -p5001 -i1
|> Tmk_startup: SWAPDIR=(null), putting swap file in "/tmp".
|> 
|> Program received signal SIG32, Real-time event 32.
|> 0x2000000000217ba2 in rt_sigsuspend () from /lib/libc.so.6.1
[...]
|> the program receives a SIG32 signal from rt_sigsuspend(..) .I am unable to
|> figure this out. 

This is normal.  SIG32 is used for communication between the thread and
the thread manager.  Use "handle SIG32 nostop noprint pass" to let gdb
handle it transparently.

Andreas.

-- 
Andreas Schwab                                  "And now for something
Andreas.Schwab@suse.de				completely different."
SuSE Labs, SuSE GmbH, Schanzäckerstr. 10, D-90443 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5


             reply	other threads:[~2001-12-01 18:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-01 18:36 Andreas Schwab [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-11-30 18:59 [Linux-ia64] pthread lib setting for ia64? Pereira, D LailaX E

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=marc-linux-ia64-105590698805567@msgid-missing \
    --to=schwab@suse.de \
    --cc=linux-ia64@vger.kernel.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