From: Ron Michael Khu <ronkhu@ntsp.nec.co.jp>
Cc: linux-c-programming@vger.kernel.org
Subject: Re: Multithreading with C++
Date: Fri, 08 Apr 2005 10:01:16 +0800 [thread overview]
Message-ID: <4255E5EC.9020107@hq.ntsp.nec.co.jp> (raw)
In-Reply-To: <D2AA47A6FB2C1A48AF0526440C0F245CAA3676@monm207.nae.ds.army.mil>
i've encountered a similar problem a few months ago...
have u tried declaring AND defining the threadfun() function OUTSIDE of
the class??
Huber, George K RDECOM CERDEC STCD SRI wrote:
>All,
>
>This may be a little off topic, but I though I would try here first.
>
>I am writting a multi-threaded program and would like to have each
>thread `managed' by a class. I have attempted to do this like this,
>using the pthreads library:
>
><code>
>====================begin cthread.h
>
>class CThread
>{
>public:
> CThread(void*);
> ~CThread();
>
> ....
>
>private:
> static CThread* m_pThis;
> pthread_t m_tid;
> static void* threadfun(void*);
>
> ....
>}
>
>==================== begin cthread.cpp
>
>CThread* CThread::m_pThis = NULL;
>
>CThread::CThread(void* arg)
>{
> int ret;
>
> m_pThis = this;
> if(0 != (ret = pthread_create(&m_tid, NULL, threadfun, arg)))
> {
> fprintf(stderr, "Thread creation failed");
> }
>}
>
>void* threadfun(void* arg)
>{
> printf("Starting thread\n");
> ....
>}
>
></code>
>
>The code compiles without warnings or errors, except when I try and
>run the application I get a segmentation fault at the pthread_create.
>Trying to run under GDB, I am able to examine the value of the
>variables and they seem consisten with what I would expect
>
>// stop on the pthread_create line in the constructor...
>
>(gdb) print m_pThis
>$1 = (CThread*) 0xfee756b0
>(gdb) print this
>$2 = (CThread*0xfee756b0
>(gdb) print m_tid
>$3 = 134514818 // to be expected because I have not initialized m_tid yet
>(gdb) print &m_tid
>$4 = (pthread_t*)0xfee756d8
>(gdb) print threadfun
>$5=&CThread::threadfun(void*)
>
>// attempt the pthread_create line ....
>
>Program received signal SIGSEGV, Segmenatation fault
>0x0000000 in ?? ()
>(gdb) where
>#0 0x00000000 in ?? ( )
>#1 0x0804a6bb in CThread (this=0xfee756b0, args=0x0) at ....
>#2 0x08049aad in daemon_main(argc=3, argv=0xfeec42d4) at ....
>#3 0x08049193 in main(argc=3, argv=0xfeec42d3) at main.cpp: 83
>
>Any idea on what is going on, or how to fix?
>
>Thanks,
>George Huber
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-c-programming" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
>
>
next prev parent reply other threads:[~2005-04-08 2:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-07 17:02 Multithreading with C++ Huber, George K RDECOM CERDEC STCD SRI
2005-04-07 16:36 ` Eric Bambach
2005-04-08 2:01 ` Ron Michael Khu [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-04-07 18:52 Huber, George K RDECOM CERDEC STCD SRI
2005-04-07 19:01 ` Darío Mariani
[not found] ` <fde202080504071322520de47@mail.gmail.com>
2005-04-07 20:26 ` Sandro Dangui
2005-04-08 6:47 Colovic (ext_evosoft) Aleksandar
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=4255E5EC.9020107@hq.ntsp.nec.co.jp \
--to=ronkhu@ntsp.nec.co.jp \
--cc=linux-c-programming@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;
as well as URLs for NNTP newsgroup(s).