|
That's a problem Subramanian ji.
When i go through Debug then i han't got assertion and when i go through normal mode then i got some time this assertion.This assertion not come regullar.So i han't got exact line of code.If it is possible then help me
|
|
|
|
|
Try different test cases and narrow down the number of cases for which the crash is occurring. You might as well output text to the debugger window from within your code (if you are not running under the VS debugger, you can still use an external debugger[^] (just connect it to the local machine) and use something like OutputDebugString[^] to print to the debugger).
The actual problem might be something as trivial as writing to a pointer that has been released, accessing memory that you don't own, etc., But you need to locate it first.
It is a crappy thing, but it's life -^ Carlo Pallini
|
|
|
|
|
Thanks for debugger information.How can i use it?
|
|
|
|
|
external debugger is not working.And i have no idia how to find assertion line plz help me
|
|
|
|
|
Provide only the code that has relevance with this issue and take your time to align the code properly.
Also, what is tr, finalstring, etc.,? There's a global tr (I don't see it declared anywhere) and another tr inside your worker thread function code with local scope. A perfect recipe for disaster.
This is one rare case where I'm going to encourage cross-posting. You may kindly cross-post your code at the coding horror forum too.
It is a crappy thing, but it's life -^ Carlo Pallini
|
|
|
|
|
Thanks Subramanian ji
i had send code where issue will be generated.And next time i align code proper.
|
|
|
|
|
Yes tr, finalstring both are globle.
Worker thread it's not tr it is tt.So sorry for that.
|
|
|
|
|
It's better if you can try out sample application with minimum code including function that cause the error that will help you to get into exact problem. And it will also helps others to find out exact cause of problem and to give appropriate solution.
|
|
|
|
|
Rajesh R Subramanian wrote: This is one rare case where I'm going to encourage cross-posting. You may kindly cross-post your code at the coding horror forum too.
|
|
|
|
|
Welcome pal.
BTW That's wonderful.
If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler.
-- Alfonso the Wise, 13th Century King of Castile.
This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong.
-- Iain Clarke
[My articles]
|
|
|
|
|
Ah, thanks. 
It is a crappy thing, but it's life -^ Carlo Pallini
|
|
|
|
|
Without looking at the code that crashed and possibly the call stack at the time of crash, nobody can help you.
Well, CPallini may be.
It is a crappy thing, but it's life -^ Carlo Pallini
|
|
|
|
|
An assertion is completely different than an exception. So which is it?
"Old age is like a bank account. You withdraw later in life what you have deposited along the way." - Unknown
"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
|
|
|
|
|
Davitor wrote: Access vilolation reading location 0xfeeefeee
0xfeeefeee is a Magic Number[^] which has a meaning. This essentially means that you are trying to access memory AFTER it has been freed. You should begin debugging by checking the variables that you are accessing in your worker thread.
Best Wishes,
-David Delaune
|
|
|
|
|
Google is your friend: try this[^].
Steve
|
|
|
|
|
Anyone can tell me How to remove segmentation fault from these program
#include<stdio.h>
#include<unistd.h>
#include<string.h>
int main()
{
char *buf;
int nread;
nread=read(0,&buf,strlen(buf)); // in these statement i am getting segmentation fault
printf("buffer size is %d\n",nread);
if(nread == -1)
{
write(2,"An error occured in read function\n",27);
}
else
{
if(nread==0)
write(2,"Data is not written to the filedescriptor\n",27);
else
write(2,"Everything went smoothly it has read the bytes\n",27);
}
}
output
sandeep@sandeep $ ./a.out <x
buffer size is 62
Everything went smoothly itSegmentation fault
|
|
|
|
|
Try:
#include<stdio.h>
#include<unistd.h>
#include<string.h>
int main()
{
char buf[128];
int nread;
nread = read(0, buf, sizeof(buf));
printf("buffer size is %d\n", nread);
...
}
|
|
|
|
|
firstly thanks
the above will work, but why not the code what i wrote,whats wrong with my code
|
|
|
|
|
sandeep_dhruwa wrote: the above will work, but why not the code what i wrote,whats wrong with my code
Are you unable to see the difference between char *buf and char buf[128]?
"Old age is like a bank account. You withdraw later in life what you have deposited along the way." - Unknown
"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 should allocate memory for you buffer and call correctly the function.
For instance:
char buf[0x100];
int nread;
nread = _read( stdin, buf, sizeof(buf));
If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler.
-- Alfonso the Wise, 13th Century King of Castile.
This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong.
-- Iain Clarke
[My articles]
|
|
|
|
|
thanks
the above may work with memset()
thank you
|
|
|
|
|
You don't need memset, you must allocate memory for the buffer (you didn't), either onto the stack (as I did) or in the heap via, for instance, malloc.
If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler.
-- Alfonso the Wise, 13th Century King of Castile.
This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong.
-- Iain Clarke
[My articles]
|
|
|
|
|
Your buf variable is an uninitialized pointer, it will surely segfault when you pass it to strlen. I also suspect that read won't work the way you think it will work, but that's just a guess right now...
> The problem with computers is that they do what you tell them to do and not what you want them to do. <
> Life: great graphics, but the gameplay sux. <
|
|
|
|
|
I want ot kwn more about multiple mark in-out design means the implementation structure. Please help me
|
|
|
|
|
ZMA_BUNTS wrote: multiple mark in-out design means the implementation structure
If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler.
-- Alfonso the Wise, 13th Century King of Castile.
This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong.
-- Iain Clarke
[My articles]
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
