From: "Russell McGuire" <rmcguire@uwbt.com>
To: <linuxppc-embedded@ozlabs.org>
Subject: Qt, forks and threads = segmentation faults?
Date: Fri, 27 Jan 2006 16:30:42 -0800 [thread overview]
Message-ID: <000301c623a2$13b98fc0$6405a8c0@absolut> (raw)
In-Reply-To: <mailman.126.1138386609.857.linuxppc-embedded@ozlabs.org>
Everyone,
This is a more general question, and if anyone knows of a more specialized
list this should be posted to, I'd be happy to do so...
Small picture of hardware:
DENX Linux 2.4.25 / PowerPC MPC8280 / 32 MBs of RAM
I am using QT Embedded for a small GUI that does BSD sockets, also using
DENX's SM501 video driver. Everything is quite stable, recently I added a
additional process to the application using fork() for the listening
'accept' call for the sockets.
After many tests I decided that due to the nature of the fork() command and
the GUI half of the program, that this was a large waste of memory, as I was
duplicating the entire GUI system. So I started looking alternatives, and
have landed at the 'pthread' library.
However, now I have lots of segmentation faults, particularly when I send a
message using QT's postEvent commands back to the main thread.
I was curious if anyone had any better idea of a more stable or perhaps a
suggestion on why I am able to only get about 30 seconds of run time out of
the app using pthread, verses fork() seems to be much stabler.
-Russ
next parent reply other threads:[~2006-01-28 0:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.126.1138386609.857.linuxppc-embedded@ozlabs.org>
2006-01-28 0:30 ` Russell McGuire [this message]
2006-01-30 9:42 ` Qt, forks and threads = segmentation faults? David Jander
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='000301c623a2$13b98fc0$6405a8c0@absolut' \
--to=rmcguire@uwbt.com \
--cc=linuxppc-embedded@ozlabs.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).