|
 truth. I know how these things work. In my case, the data was longer than the communications buffer. Since the code one uses the communications buffer to talk to the hardware, the last 30 bytes or so were being dropped.
thanks
Charlie Gilley
<italic>Stuck in a dysfunctional matrix from which I must escape...
"Where liberty dwells, there is my country." B. Franklin, 1783
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
|
|
|
|
|
Well, the Packing pragma is very old. A Pragma is an adidional instruction to the compiler,stated in te file to be compiled. In the Packing case, it is about how to align data on Preferred Data Boundaries. A 64 bit CPU is most efficient if all items are stored at addresses, a multiple of 64. Failing to do so, the code will not break down. it will just take (very minutely) longer to execute, but will never break your code.
Now, you can Easily enter "Packing Hell"! That occurs when different packing pragma's are used in different components. Unless if something is critical, the best idea is to leave all packing pragments out, unless you have reasons to use them, e.g. Interfacing a new 64 structure with say old 16 or 32 bit data.
Bram van Kampen
|
|
|
|
|
In general all struct items are aligned to word boundaries, so you should be able to draw the layout just by reading the source. However, if you use the #pragma pack directive anywhere then it tends to move things closer together. But without seeing any of your code it's impossible to say more.
|
|
|
|
|
good comments all. I've been around the block, so I'm certain that due to the compiler's desire to arrange things in a preferential way. I've just started digging into this code for another issue and blundered into this one. The structure is stored as a blob in the system, so I must be very, very careful in how I touch this structure. Changing any of the alignment options will surely frag stored data.
This leads me to realize that all one needs to do is change the packing on the compiler line, and the data will be trashed. Oh, but wait, it gets worse. This code base is built with two different IDEs. It's vulnerable there as well.  It's 8am on a Sunday, and I have a long day ahead of me.
Charlie Gilley
<italic>Stuck in a dysfunctional matrix from which I must escape...
"Where liberty dwells, there is my country." B. Franklin, 1783
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
|
|
|
|
|
I have a C++ project that was created in qt creator. (but doesn't use any of its features) Is there a way to painlessly migrate it to visual studio? There is Qt tools for visual studio but it requires downloading a bunch of different stuff to make it work and assumes you are making a qt project.
I've tried manually adding the files to visual studio but for some bizarre reason there is no easily visible option to add existing folders forcing me to manually create folders one by one and add the files into it. https://shareit.onl/
modified 13-May-21 5:18am.
|
|
|
|
|
Do you have make / cmake files there ? These ones could help you.
|
|
|
|
|
The make/cmake is probably full of qt references.
CI/CD = Continuous Impediment/Continuous Despair
|
|
|
|
|
1. Create an empty project in Visual Studio.
2. Copy the files into the project directory.
3. In Visual Studio go to the Solutions window where you can add the files to their proper (virtual) folder (Header, Resource or Source).
4. You may then need to adjust the Project settings to build the project correctly.
|
|
|
|
|
Hello everyone I was required to build my first Arduino game and I still do not control well will be happy for your help
Light a random position in both the directions and diagonals represented by two bulbs
That is, if for example: both the right and the top light are on - move diagonally to the right and up and turn both off
And after 20 times of correct moves turn off the lights and let the game end.
|
|
|
|
|
I see no code in your post.
"In testa che avete, Signor di Ceprano?"
-- Rigoletto
|
|
|
|
|
|
Hi
In the process of re-writing my CAsyncSocket to the more controllable WSA flavor I got stuck on WaitForMultipleObjects.
For Each Event on the socket that I do a bind by that I mean FD_READ, FD_WRITE I CreateEvent I associate the events with WSAEventSelect.
I pass all the info (HWND windows message etc when I want notification to be sent in a structure) pointed to by a LPVOID the parameter in The CreateThread
I let the worker thread wait on the events and do the appropriate SendMessage
Problems is I am abending or rather getting an Access violation on WaitForMultipleobjects
Running under the visual studio debugger I can see the values of the 5 events are correct
The first thing i thought of was that my worker thread didnt have security rights to the events I created in the Mother thread ( all threads are in the same process)
I just figured the quickest way to resolve this was to name the events and do a OpenEvent If I get a null from any events I would have a problem
All of the events named from OpenEvent return a value however they are not the same event values that I created
Real mystery to me
Hope some one can help
Thanks
|
|
|
|
|
ForNow wrote:
I let the worker thread wait on the events and do the appropriate SendMessage
Should you be using PostMessage() instead?
"One man's wage rise is another man's price increase." - Harold Wilson
"Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons
"You can easily judge the character of a man by how he treats those who can do nothing for him." - James D. Miles
|
|
|
|
|
You mean like this the worker thread doesn’t have to wait for a reply from send message
Ok thanks
|
|
|
|
|
Do you pass any MFC object to the worker thread?
|
|
|
|
|
No not sure how WSAWaitForMultipleEvents is implemented in Windows MFC app
But it was always my understanding based on feedback from people such as yourself that any kernel object wait I.E WaitForSingle/Multiple should be done in a worker thread correct ?
|
|
|
|
|
ForNow wrote:
No not sure how WSAWaitForMultipleEvents is implemented in Windows MFC app
But it was always my understanding based on feedback from people such as yourself that any kernel object wait I.E WaitForSingle/Multiple should be done in a worker thread correct ? |
WSAWaitForMultipleEvents has nothing to do with MFC (note that it is defined in Winsock2.h header!).
And what does it have to do with your using WaitForMultipleObjects function? 
|
|
|
|
|
I am using WaitForMultipleObjects rather thanWSAWaitForMultipleEvents for socket notification regardless don’t think the wait should be in the main thread
|
|
|
|
|
ForNow wrote: don’t think the wait should be in the main thread
If you would implement the Wait... in the main thread then you could wait forever and your main thread could be frozen forever.
BTW, how do you create/obtain the event HANDLEs that you pass in the WaitForMultipleObjects? Are they all correct?
modified 10-May-21 10:37am.
|
|
|
|
|
I am using CreateEvent as it gives me more flexibility i.e auto reset As opposed to WSACreateEvent I then pass everything in a structure pointed to by LPVOID had to build it with no alignment (Zp1) as I was getting slack bytes among members of the structure
thanks
|
|
|
|
|
Could you post some code snippets describing what you do?
|
|
|
|
|
sure be glad to in fact I appreciate it Am at work now (I work as a z/os Mainframe assemnbler programmer ) this has given me a chance to enhance my skills its 10:50 am here EST get off of work 5:00 - 5;30 will do it then thanks for your help
|
|
|
|
|
ForNow wrote: I pass all the info (HWND windows
The MFC framework does not always give you the *real* HWND to a window. As strange as this might sound, the MFC framework maintains two object maps. The 'real objects' and an internal 'temporary handle map'. MFC will sometimes give you a temporary CTempWnd instead. If you are passing the window handle of a MFC class then you need to use CWnd::GetSafeHwnd[^]. There are some rare occasions where GetSafeHwnd cannot give you the real window handle and will return NULL instead so you should probably check for that too.
Not many people are using MFC these days. You should consider moving on.
I can't think of much else that would cause WaitForMultipleObjects to throw an access violation. The only other thing I can think of... is a corrupt heap. Sounds like you are somehow passing garbage to WaitForMultipleObjects.
Best Wishes,
-David Delaune
|
|
|
|
|
Thanks I had some other problems
I got rid of the WaitForMultipleObjects and set all my notifications on one event and extracted the correct one with WSAENumnetwork that worked when you say not many people are using MFC do yo mean they coding Windows C API
I found CAsynsockets to be a pain I couldn’t pass along notification to another window
Thanks
|
|
|
|
|
ForNow wrote: when you say not many people are using MFC do yo mean they coding Windows C API
I found CAsynsockets to be a pain I couldn’t pass along notification to another window
I guess he meant they use C#.
I used CAsyncSocket class successfully since many years (until I have changed the company to work for). I never had any problems with this class to work with both IPv4 and IPv6 sockets in IPC with multiple sockets through intranet and internet.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
