StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POC++ queue doesn’t like less than 8 char*s
primarykey
Id
6759902
data
AcceptedAnswerId
6760227
AnswerCount
2
ClosedDate
CommentCount
3
CommunityOwnedDate
CreationDate
2011-07-20T09:42:08.490
FavoriteCount
0
LastActivityDate
2011-07-21T07:58:18.927
LastEditDate
2011-07-20T10:06:06.027
LastEditorUserId
757750
OwnerUserId
757750
ParentId
0
PostTypeId
1
Score
1
ViewCount
226
LastEditorDisplayName
text
Body
A program written in C++ reads from a network socket and then writes to local socket. It uses a separate thread for the “read”. When a message is read, it is put into a char * queue (using mutex from the boost libraries to make it thread-safe). Meanwhile the queue is checked to see if it is empty, if it isn’t, then the first message is popped from the queue (again using mutex) and written to the local socket as a char *. My issue is: when a message of 4 bytes is pushed onto the queue, the queue saves it without issue, however when writing the message back out again, it has increased the message to eight bytes! The “new” four bytes are zero. <hr> Example A <pre><code>Message in: {4,0,0,0} Saved to queue as; <4>, <0>, <0>, <0> Read from queue as: <4>, <0>, <0>, <0>, <0>, <0>, <0>, <0> </code></pre> <hr> Example B <pre><code>Message in: {4,0,0,0,8,0,0,0} Saved to queue as; <4>, <0>, <0>, <0>, <8>, <0>, <0>, <0> Read from queue as: <4>, <0>, <0>, <0>, <8>, <0>, <0>, <0> </code></pre> <hr> Any ideas as to the reason for this? Can the queue class only cope with a minimum number of chars? (Wouldn’t have thought so as there’s the “empty” method). (This isn’t a major issue, as I never talk in less than eight bytes; I just want to know in case it comes up and attacks me later on in life.) I did a bit of digging around online and through the documentation and found the odd referece to a buffer, but that seems to be more to do with using the queue as a buffer, rather than it having one... Other information; OS: RedHat IDE: Eclipse <hr> Code: Queue <pre><code>//Thread-safe call to save the message to the queue void MessageQueue::SaveToQueue(char* Data) { // Lock the mutex to prevent any other threads accessing this member (released when method exits). boost::mutex::scoped_lock l(m_Msg); //int i = 0; //while (i < sizeof(Data))//iLength) //{ // unsigned int ByteVaule = Data[i];//pBuffer[i];//ByteValue = int(pBuffer[i]);//unsigned int(pBuffer[i]); // cout << "Buffer in Queue" << i << ": " << ByteVaule << endl; // i++; //} MsgQ.push(Data); } //Thread-safe call to get the message from the queue char* MessageQueue::GetFromQueue() { // Lock the mutex to prevent any other threads accessing this member (released when method exits). boost::mutex::scoped_lock l(m_Msg); char* message = MsgQ.front(); MsgQ.pop(); return message; } //Thread-safe call to check if the queue is empty bool MessageQueue::IsEmpty() { // Lock the mutex to prevent any other threads accessing this member (released when method exits). boost::mutex::scoped_lock l(m_Msg); return MsgQ.empty(); } </code></pre> <hr> Code: Manager int iStatus = 0; <pre><code>//Start class to store message queue MessageQueue* pQueue = new MessageQueue(); // Current hard coded value for the write scoket location // TODO: change this to reading from enviroment variable string WritePath = "DefaultSocket"; ReadSocket* pRead = new ReadSocket(); WriteSocket* pWrite = new WriteSocket(); cout << "Creating read socket" << endl; iStatus = pRead->CreateSocket(pQueue); cout << "Creating write socket." << endl; iStatus = pWrite->CreateSocket(WritePath); //while is running, check the message container and process it as needed while (pRead->IsRunning()) { while (!(pQueue->IsEmpty())) { char* Msg = pQueue->GetFromQueue(); iStatus = pWrite->WriteToSocket(Msg); // TODO: catch on failure } //sleep(1); } //Destroy sockets as program is closing pWrite->~WriteSocket(); pRead->~ReadSocket(); // TODO: add exception? //Token return return iStatus; </code></pre> <hr> To save making this too long and complex the read and write sockets are the same as in <pre><code>http://www.linuxhowtos.org/C_C++/socket.htm </code></pre> The read char* is saved to the queue using the <pre><code>SaveToQueue() </code></pre> method and taken from the queue using the <pre><code>GetFromQueue </code></pre> method.
Tags
<c++><eclipse><queue><redhat>
Title
C++ queue doesn’t like less than 8 char*s
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USAndy
UserOwnerUserId
1. USAndy
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. VO
 singulars
 PostPostId
 POC++ queue doesn’t like less than 8 char*s
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.