public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Kang Kai <Kai.Kang@windriver.com>
To: gaowanlong@cn.fujitsu.com
Cc: ltp-list@lists.sourceforge.net
Subject: [LTP] POSIX pthread_detach/4-3 fails with SIGSEGV randomly
Date: Tue, 14 Aug 2012 10:06:40 +0800	[thread overview]
Message-ID: <5029B2B0.5080603@windriver.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1300 bytes --]

Hi Wanlong,

Case pthread_detach/4-3 fails with SIGSEGV randomly on x86_64 with 
Ubuntu 11.10.
I saw that you have made a patch for it. So would you like to give me 
some advice to solve it? Thanks.
It seems a multi-threads issue and I have try to debug with the core 
file but not much help.

The fail log:
[09:58:38]System abilities:
[09:58:38] TSA: 200809
[09:58:38] TSS: 200809
[09:58:38] TPS: 200809
[09:58:38] pagesize: 4096
[09:58:38] min stack size: 16384
[09:58:38]WARNING: The TPS option is claimed to be supported but 
setscope fails
[09:58:38]WARNING: The TPS option is claimed to be supported but 
setscope fails
[09:58:38]WARNING: The TPS option is claimed to be supported but 
setscope fails
[09:58:38]WARNING: The TPS option is claimed to be supported but 
setscope fails
[09:58:38]WARNING: The TPS option is claimed to be supported but 
setscope fails
[09:58:38]WARNING: The TPS option is claimed to be supported but 
setscope fails
[09:58:38]WARNING: The TPS option is claimed to be supported but 
setscope fails
[09:58:38]WARNING: The TPS option is claimed to be supported but 
setscope fails
[09:58:38]WARNING: The TPS option is claimed to be supported but 
setscope fails
[09:58:38]All 33 thread attribute objects were initialized

Segmentation fault (core dumped)

Regards,
Kai

[-- Attachment #1.2: Type: text/html, Size: 1831 bytes --]

[-- Attachment #2: Type: text/plain, Size: 395 bytes --]

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/

[-- Attachment #3: Type: text/plain, Size: 155 bytes --]

_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

                 reply	other threads:[~2012-08-14  2:08 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=5029B2B0.5080603@windriver.com \
    --to=kai.kang@windriver.com \
    --cc=gaowanlong@cn.fujitsu.com \
    --cc=ltp-list@lists.sourceforge.net \
    /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