Mail Archives: cygwin/2007/03/08/12:34:15
No, I don't think that my program has a bug.
Ok, this is the code of my program (C):
#include <stdio.h>
int main ()
{
printf("hello");
return 0;
}
Another code with the same problem (Segmentation fault)
int main ()
{
return 0;
}
And I could follow writting codes because all have the same problem.
> we don't have your machine,
I said that I only get that problem in this computer (a laptop with windows
xp media center, intel core 2 duo t5600)
> you haven't given an adequate description of the problem.
Do you say that for my english? (if so, I'm sorry but cannot do more)
If not, then tell me what I must explain more.
"Dave Korn" <dave DOT korn AT artimi DOT com> escribió en el mensaje
news:039501c761a3$58af5e80$2e08a8c0 AT CAM DOT ARTIMI DOT COM...
> On 08 March 2007 14:43, Raymond Miller wrote:
>
>> Finally I found what is the problem.
>
> No, I don't think you have. You haven't even clearly identified a
> problem.
>
> You say that the problem is that gdb reports a SIGSEGV in thread 2 when
> you
> compiled with cygwin gcc, but for all anyone knows that could just be
> because
> your program caused a crash and thread 2 is the signal-handling thread in
> cygwin programs.
>
> When you compile with mingw's gcc, you are compiling an entirely
> different
> program, because mingw doesn't support all the posix things like signals
> etc.
> that cygwin supports.
>
>> Is it a bug in that version?
>
> Again, nobody can tell. We don't have your code, we don't have your
> machine, you haven't given an adequate description of the problem. Just
> going
> by sheer balance of probabilities, however, it is far more likely that gcc
> is
> doing the right thing and your program has a bug in it.
>
> cheers,
> DaveK
> --
> Can't think of a witty .sigline today....
>
>
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
- Raw text -