C / C++ / MFC

Re: chat window to chat urgent please ?

9-Aug-07 0:14

Download here[^], and be happy Cool | :cool:

[VisualCalc][Binary Guide][CommDialogs] | [Forums Guidelines]

Re: yes, certainly. here

p_9-Aug-07 0:29

9-Aug-07 0:29

thanks for this sir
but i want it through coding in vc++
thanks Rose | [Rose]

Re: yes, certainly. here

tyagineha9-Aug-07 0:41

tyagineha

9-Aug-07 0:41

hye,
i m also looking for this topic...
can u send me ur project.
my id is gemini_5jun@yahoo.com

Re: yes, certainly. here

p_9-Aug-07 0:58

9-Aug-07 0:58

i am sorry becoz my project is not complete
and i am working on it
i have only forms and login coding for user

SnaKeBeD9-Aug-07 2:29

SnaKeBeD

9-Aug-07 2:29

hi master,

hope u are still searcing for the answer, search the article in code project for vc++ code for LAN chatting .If u need the code for Internet chat please reply or mail me Roll eyes | :rolleyes:

...

swaroop

Re: chat window to chat urgent please ?

p_9-Aug-07 21:12

9-Aug-07 21:12

thanks sir\
please send me that sir
again thanks

Re: chat window to chat urgent please ?

David Crow9-Aug-07 3:23

David Crow

9-Aug-07 3:23

So exactly which part do you need help with? What do you have working so far?

"A good athlete is the result of a good and worthy opponent." - David Crow

"To have a respect for ourselves guides our morals; to have deference for others governs our manners." - Laurence Sterne

User breakpoint called from code at 0x77f813b1

Rajasegar8-Aug-07 23:31

8-Aug-07 23:31

I am trying to debug a program in release build.
But after some time i getting a message like

"User breakpoint called from code at 0x77f813b1"

how to rectify this one?
What actually is the problem here?
Please help me.............

R@j@$eg@r

toxcct8-Aug-07 23:41

8-Aug-07 23:41

have you set a breakpoint somewhere ?

have you tried to step into the debugger and watch your variables to understand why it was crashing ?

BTW, what's your IDE ?

[VisualCalc][Binary Guide][CommDialogs] | [Forums Guidelines]

Rajasegar8-Aug-07 23:43

8-Aug-07 23:43

No, I removed all the breakpoints in my program.

Actully i am using Visual studio 6.0...

R@j@$eg@r

[Message Deleted]

toxcct8-Aug-07 23:47

8-Aug-07 23:47

[Message Deleted]

Mark Salsbery9-Aug-07 5:56

Mark Salsbery

9-Aug-07 5:56

toxcct wrote:
you cannot debug a program compiled in release mode

Hogwash

Mark Salsbery
Microsoft MVP - Visual C++
Java | [Coffee]

Stephen Hewitt9-Aug-07 20:09

Stephen Hewitt

9-Aug-07 20:09

I come across this misconception all the time; there is no truth to it. There is nothing to stop you from enabling debug information for release builds. I do it all the time. The only issue is the MSVC IDEs don’t do this by default. If I made it they would.

Steve

toxcct9-Aug-07 21:21

9-Aug-07 21:21

we're talking about a user who don't even know the fundamental differences between debug and release... do you think he could have customized its settings by any chance ? Unsure | :~

[VisualCalc][Binary Guide][CommDialogs] | [Forums Guidelines]

Stephen Hewitt9-Aug-07 21:24

Stephen Hewitt

9-Aug-07 21:24

My response was to your assertion that, "you cannot debug a program compiled in release mode". This is simply not true.

Steve

jhwurmbach8-Aug-07 23:44

jhwurmbach

8-Aug-07 23:44

Rajasegar wrote:
I am trying to debug a program in release build.

Why?
You definitely should use the debug build for that.

Though I speak with the tongues of men and of angels, and have not money, I am become as a sounding brass, or a tinkling cymbal.
George Orwell, "Keep the Aspidistra Flying", Opening words

Rajasegar8-Aug-07 23:47

8-Aug-07 23:47

Okay, we used to debug from release builds in our development environment,
btw i will try to debug it from debug build, will this solve my problem,
but i would like to know what exactly is the problem...........

R@j@$eg@r

toxcct8-Aug-07 23:48

8-Aug-07 23:48

Rajasegar wrote:
but i would like to know what exactly is the problem...........

how can we know ?

[VisualCalc][Binary Guide][CommDialogs] | [Forums Guidelines]

KaЯl9-Aug-07 0:03

KaЯl

9-Aug-07 0:03

Often this problem comes from memory which was corrupted somewhere in the application. So check in your code if you do not write outside an array, work with freed pointers, and so on.

Jouir et faire jouir sans faire de mal ni à toi ni à personne, voilà je crois le fondement de toute morale

Fold with us! ¤ flickr

Jelahd9-Aug-07 0:21

Jelahd

9-Aug-07 0:21

You can debug from release mode if you build with program database and switch off the optimization.
The debugger looks for the PDB file and will load it if present.
Change project setting in C/C++ General Tab to disable(debug) optimization and create Debug Info in Program Database.
Optimization can shuffle code around and remove redundant stuff which can confuse the debugger because the binary does not match the source.

Good Luck.

Rajasegar9-Aug-07 0:32

9-Aug-07 0:32

hi,

thanx for the reply buddy....

This problem still persists in both the release and debug builds of the same program. Initially i tried to debug in release build, but now i tried it in debug build, and now also i am getting the same message, i have tried the settings you mentioned, but still the message appears....

R@j@$eg@r

toxcct9-Aug-07 0:35

9-Aug-07 0:35

Read this[^]

[VisualCalc][Binary Guide][CommDialogs] | [Forums Guidelines]

jhwurmbach9-Aug-07 0:42

jhwurmbach

9-Aug-07 0:42

Rajasegar wrote:
but now i tried it in debug build, and now also i am getting the same message

Ok.
The debugger should show you where in the code the error occures.
Maybe you need to user the "Call Stack" window to step up the call stack to your code.
There you should be able to find the problem.

Though I speak with the tongues of men and of angels, and have not money, I am become as a sounding brass, or a tinkling cymbal.
George Orwell, "Keep the Aspidistra Flying", Opening words

Jelahd9-Aug-07 6:02

Jelahd

9-Aug-07 6:02

Should have said that the suggestion will only help you debug a release version of an app. Not necessarily find this specific problem.
You could try the Exception dialog in the Debug menu. Only available during debugging. It lets you control debugger behaviour in the event of an exception. Can be useful but time consuming.