|
Mark Salsbery wrote: make sure you are doing a debug build, not a release build of your application.
Yeh it is a debug build only well Debug is in selected mode in MS vs or is there any other way to check for debug mode then let me know if not then yes its in debug mode.
Both the option give me same error.
Mark Salsbery wrote: 1) switch(uMsg){
When cursor goes to next line it returns FALSE and then i get same error
Mark Salsbery wrote: On any of the function calls.
Nopes same error.
|
|
|
|
|
Software_Specialist wrote: When cursor goes to next line it returns FALSE and then i get same error
At runtime? With a breakpoint on the switch statement?
Software_Specialist wrote: Both the option give me same error.
What kind of error??
Mark
"Posting a VB.NET question in the C++ forum will end in tears." Chris Maunder
|
|
|
|
|
Mark Salsbery wrote: At runtime? With a breakpoint on the switch statement?
Yeh i placed break pt over switch(uMsg) and when cursor stops at dis pt then next jump it takes to return False and immidiately after crossing close bracket } it gives me error saying "There is no source code available for the current location."
Mark Salsbery wrote: What kind of error??
"There is no source code available for the current location."
I tried with another VC++ application aswell and it also gives me same kind of error. Ill try copying the code to new project and see if i face same problem or not.
Thanks
|
|
|
|
|
Now i tried to re-build the application and it is giving me loads of errors like
Cannot convert parameter 2 from 'const char[6]'to'LPCWSTR'.
And many others similar to the above.
Well i guess this application is written in some older version of VC++ compiler and now when i tried to compile it over VS2005 i got a message saying
"The project 'abc.dsp' must be converted to the current Viusal C++ project format. After it has converted, you will not be able to edit this project in previous version of Visual Studio."
So what does this mean. Is the problem related to this.
Pls let me knw
Thanks
|
|
|
|
|
Software_Specialist wrote: Now i tried to re-build the application and it is giving me loads of errors like
Cannot convert parameter 2 from 'const char[6]'to'LPCWSTR'.
Somehow you've changed the project settings to make a unicode build. If that's your intention
then you're going to have to fix your code to use Unicode.
Software_Specialist wrote: "The project 'abc.dsp' must be converted to the current Viusal C++ project format. After it has converted, you will not be able to edit this project in previous version of Visual Studio."
Make a backup of the old project - everything. Just in case you have to go back to the old VC
version. Then you can let the new VS convert the project to be compatible with the current
version.
Mark
"Posting a VB.NET question in the C++ forum will end in tears." Chris Maunder
|
|
|
|
|
Software_Specialist wrote: Yeh i placed break pt over switch(uMsg) and when cursor stops at dis pt then next jump it takes to return False
That's because you'll get alot of messages in your DialogProc that you haven't handled in your
switch statement. A breakpoint there will stop on every message - there will be alot of them.
If you want to catch WM_INITDIALOG, then put a breakpoint at the code after "case WM_INITDIALOG:".
Software_Specialist wrote: "There is no source code available for the current location."
That's not an error. That means you are trying to step into code that doesn't have debug info
available to match up source code with machine code. In that case you can only step in via
the disassembly window.
There's nothing strange going on. You need breakpoints in YOUR code 
Mark
"Posting a VB.NET question in the C++ forum will end in tears." Chris Maunder
|
|
|
|
|
Hi,
sometimes I can't use the debug breakpoints for A or B reason... When that happens... I use AfxMessageBox (...) / MessageBox (NULL,...).
You can not have lots of info, but at least you can determine when it chrashes by moving the message up and down (or with 2 or 3 and different messages). Once you know exactly WHERE, is easier to determine WHAT.
Greetings
--------
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
|
|
|
|
|
Hello,
I'm receiving a windows message box (actual name of EXE omitted):
First-chance exception in ______.exe: 0xC0000005: Access Violation
Possible deallocation error? Any other ideas what the problem may be? Any help is appreciated. The disassembly code is shown below (crash at line 44).
38: void CPlex::FreeDataChain()
39: {
00479931 test ecx,ecx
00479933 je CPlex::FreeDataChain+15h (00479946)
00479935 push esi
40: CPlex* p = this;
41: while (p != NULL)
42: {
43: BYTE* bytes = (BYTE*) p;
44: CPlex* pNext = p->pNext;
<code>00479936 mov esi,dword ptr [ecx]</code>
45: delete[] bytes;
00479938 push ecx
00479939 call operator delete (0047f53d)
0047993E pop ecx
0047993F test esi,esi
46: p = pNext;
00479941 mov ecx,esi
00479943 jne CPlex::FreeDataChain+5 (00479936)
00479945 pop esi
47: }
48: }
Regards,
Mike
|
|
|
|
|
Either the caller provied a bad this (but non-NULL) pointer or the linked list structure is corrupt.
Steve
|
|
|
|
|
Looking at this piece of code, i got the shivers. 
Well it is MFC code so I shouldn't be surprised.
Use the call stack to get back to get to your code where the real problem probably occurred.
Check for already delete of freed up chunks of memory.
codito ergo sum
|
|
|
|
|
The problem has been solved. It turns out that I was allocating an incorrect amount of memory for three variables. To sum up,
Old:
double *var1 = new double[20];
Changed to:
double *var1 = new double[correctInt];
Regards,
Mike
|
|
|
|
|
Hi Guys,
Some background info:
OS - Windows XP Home SP2
IDE - Visual Studio 2002 .NET
I am writing a small client/server application to send/receive data over a network based on WSASocket. Everything is working as the client connects to the server and data is passed successfully between them, except for one issues...
At this stage I am running both the server and client on my development PC and am connecting to 127.0.0.1 or the network ip of 192.168.1.1
Sometimes (about 1 in 10) the establishment of the connection takes a long time, up to 30 seconds. I have now traced the server and client programs to death and now came to the conclusion that the actual firing/receiving of the FD_ACCEPT event sometimes takes very long, for now apparant reason, although usually the FD_ACCEPT is fired within 100ms.
I've traced out the applications to the point where I can show the actual timestamps of the connect function call and the corresponding reception of the FD_ACCEPT event.
To further confuse things it seems that this problem never occurs when I disconnect the network cable. Without the cable I've done about 50 connection tests and they all work fine. When I plug the network cable into the nic every now and then the connection takes an age to establish.
Does anybody have any idea what is going on here ? Is it a nic driver problem ? Is it a winsock problem ? Is it a Windows problem ? Any other ideas ?
Thanks
OD
|
|
|
|
|
What method are you using to obtain the FD_ACCEPT notification? Window message? Event?
Mark
"Posting a VB.NET question in the C++ forum will end in tears." Chris Maunder
|
|
|
|
|
Hi Mark,
Here is the code :
TRACE("\nCheckEvents 1 - %s", CDateTimeTools::TimeString());
if (WSAWaitForMultipleEvents(1, &m_hEvents, FALSE, 60000, TRUE) >= WSA_WAIT_EVENT_0)
{
TRACE("\nCheckEvents 2 - %s", CDateTimeTools::TimeString());
WSAResetEvent(m_hEvents);
WSANETWORKEVENTS sEvents = {0};
if (!WSAEnumNetworkEvents(m_hSocket, m_hEvents, &sEvents))
etc, etc, etc ...
With the time difference between TRACE 1 and 2 being in the region of 30 seconds when things go wrong !
Cheers
|
|
|
|
|
IS that code used after the connect call()?
Also, you can remove the WSAResetEvent(m_hEvents); call. WSAEnumNetworkEvents() will do the
reset for you.
Regardless, 30 seconds is typically the default timeout for sockets searching for a remote
address. In the client, make sure the address struct for the server address is initialized
correctly. If connect() was finding the remote address - even if a server wasn't listening on
the connect port - it would fail in a few seconds max, not 30 seconds.
Mark
"Posting a VB.NET question in the C++ forum will end in tears." Chris Maunder
|
|
|
|
|
Jip, that is the code that waits for events on the server side. The point is still that every once in a while only the problem occurs that the FD_ACCEPT event is fired after about 30 seconds and though even though it is slow, the connection is then accepted and functions fine onwards.
Cheers
|
|
|
|
|
Hmmm not likely related to the code I've seen so far...
od@ananzi.co.za wrote: and am connecting to 127.0.0.1 or the network ip of 192.168.1.1
If you use "ipconfig" from a command prompt, what's the IP address of your machine?
Is it 192.168.1.1? That's always been my LAN router address.
Can you post the code that builds the sockaddr for both the connect() call on the client and the
bind() call on the server?
I'm not sure why it would be slow only sometimes...the 30 seconds time still says
network/addressing to me...
Mark
"Posting a VB.NET question in the C++ forum will end in tears." Chris Maunder
|
|
|
|
|
Haven't seen this problem in my networking applications.
Additionally to Mark's comments: The only things I can guess is that your event handling may has a problem -or- your connect call is not IP based and the DNS-resolution for a hostname blocks a while. The server socket should get the FD_ACCEPT practically immediately inside the LAN (<50ms).
|
|
|
|
|
I haven't been able to make any headway as to what the problem/cause is, but some other thoughts ...
Although the application is running on my PC locally, my PC is connected on a nationwide VPN over ADSL. At this stage I am thinking that maybe somehow the routing tables in my tcp/ip stack gets screwed/reset/cleared and that the connection attempt then first "goes out" onto the VPN, before being handled by my application anyway.
I am going to try and snoop the network packets at some stage to try and verify my guess.
Cheers
|
|
|
|
|
Just checking one thing... are you working IP-based or hostname-based in your connect call?
|
|
|
|
|
I have tried both in my connect call, ip and hostname, and both does the slow connect thing without any discernable difference in the frequency of the problem appearing.
|
|
|
|
|
Sorry out of generic ideas, this must not happen! Have a good look at your networking core and try to stress test it isolated from application logic. If it is not a private/research project your are working one I would even consider using an existing network class (CAsyncSocket, IpWorks, etc).
|
|
|
|
|
Hi Moak. I'm out of ideas as well, except that I can now confirm that this problem does not occur when the application are running on a "pure" lan, i.e. no gateways/breakouts/links/etc to our VPN. It is only when I run the applications on PC's that are connected to the VPN that this problem occurs.
But my most technical response to the problem no is: Go Figure !
|
|
|
|
|
Hmmm, sounds like trouble! How about using a different networking library? If you search this forum you will find some suggestions (CAsyncNetwork, IpWorks, etc).
/M
PS: In case you are not sure which to use... feel free to try mine, follow link from my user page and download the SDK
|
|
|
|
|
Err, which link would that be ?
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
