Ok, I have the core dump files of the program that crashed, how do I analyze them?

Thank you!


In article <41263AA7.57392D4E@wikiservice.at>, Helmut Leitner says...
>
>
>
>"Martin (very worried)" wrote:
>> 
>> See: "to Walter: important BUG (I think)"
>> 
>> Error on a very low level of the D language is a very big problem and I think it must be handled very quiqkly.
>> 
>> >This looks like it could be a problem with stack overflows.
>> 
>> Yes, and it looks like it is an error in compiler. It is not a server error, because everything elese works fine. It is not a cgi error, because I tested it also direct throw ssh.  And I don't thik there is an error in my program, because it is very simple and there is nothing there that could cause a "Segmentation fault".
>> 
>> I dested it with 0.99, nothing changed.
>> 
>> SO DO YOU WANT THE CORE DUMP FILES(I think they include the memory image of the
>> prgogram, at the moment of segmentation fault)?
>> If you do, where do I send them?
>> if you don't, tell me, I stop offering then.
>
>Martin, you are surely not ignored and there are at least a dozen people here that take this error seriously.
>
>I just found the time to compile and test your code under Suse Linux 9.1 and gcc 3.3.3, dmd 0.98. I did 1225551 runs total without a single fault.
>
>You seem to be sure it is a compiler fault.  I'm not so sure about the cause of this error. Maybe its your system or gcc.
>
>-- 
>Helmut Leitner    leitner@hls.via.at
>Graz, Austria   www.hls-software.com

I works perfectly in valgrind.
I tried 200 runs in valgrind, 0 errors.
I tried 200 runs without valgrind, got 14 crahses.

What do I do?




In article <cg5jtj$lmm$2@digitaldaemon.com>, Daniel Horn says...
>
>try running it in valgrind?
>
>Helmut Leitner wrote:
>> 
>> "Martin (very worried)" wrote:
>> 
>>>See: "to Walter: important BUG (I think)"
>>>
>>>Error on a very low level of the D language is a very big problem and I think it must be handled very quiqkly.
>>>
>>>
>>>>This looks like it could be a problem with stack overflows.
>>>
>>>Yes, and it looks like it is an error in compiler. It is not a server error, because everything elese works fine. It is not a cgi error, because I tested it also direct throw ssh.  And I don't thik there is an error in my program, because it is very simple and there is nothing there that could cause a "Segmentation fault".
>>>
>>>I dested it with 0.99, nothing changed.
>>>
>>>SO DO YOU WANT THE CORE DUMP FILES(I think they include the memory image of the
>>>prgogram, at the moment of segmentation fault)?
>>>If you do, where do I send them?
>>>if you don't, tell me, I stop offering then.
>> 
>> 
>> Martin, you are surely not ignored and there are at least a dozen people here that take this error seriously.
>> 
>> I just found the time to compile and test your code under Suse Linux 9.1 and gcc 3.3.3, dmd 0.98. I did 1225551 runs total without a single fault.
>> 
>> You seem to be sure it is a compiler fault.  I'm not so sure about the cause of this error. Maybe its your system or gcc.
>> 

Martin wrote:
> I works perfectly in valgrind.
> I tried 200 runs in valgrind, 0 errors.
> I tried 200 runs without valgrind, got 14 crahses.
> 
> What do I do?

Have you tried DMD 0.100 ?

NOW INT FORKS FINE. thank you Walter, thank you all!

For a second, I was afraid, that I need to move back to C.
(Ok, there are always ways to workaround bugs, but when my program has to work
correctly atleast 99.9998% of times that it's executed, then I am glad, that
this bug is fixed)

My job is to write a cgi web application and it was my personal choice to use D for it. So you know why i was so nervous.

Ok, now I will continue with my project my deadline is coming very fast.
D is a very good language for writing web (a lot better than PHP, or Java, or
even better than C).
So I reccomend it for that use.
(Hopefully there are no more big bugs, but even when there are, hope they can be
fixed. I have even seen some bugs in GNU C, so nothing is perfect)


In article <cg7g0h$1uu6$1@digitaldaemon.com>, h3r3tic says...
>
>Martin wrote:
>> I works perfectly in valgrind.
>> I tried 200 runs in valgrind, 0 errors.
>> I tried 200 runs without valgrind, got 14 crahses.
>> 
>> What do I do?
>
>Have you tried DMD 0.100 ?

Sorry, spelling mistake, what I ment was:
NOW IT FORKS FINE. thank you Walter, thank you all!

In article <cg8brq$2d3n$1@digitaldaemon.com>, Martin says...
>
>NOW INT FORKS FINE. thank you Walter, thank you all!
>
>For a second, I was afraid, that I need to move back to C.
>(Ok, there are always ways to workaround bugs, but when my program has to work
>correctly atleast 99.9998% of times that it's executed, then I am glad, that
>this bug is fixed)
>
>My job is to write a cgi web application and it was my personal choice to use D for it. So you know why i was so nervous.
>
>Ok, now I will continue with my project my deadline is coming very fast.
>D is a very good language for writing web (a lot better than PHP, or Java, or
>even better than C).
>So I reccomend it for that use.
>(Hopefully there are no more big bugs, but even when there are, hope they can be
>fixed. I have even seen some bugs in GNU C, so nothing is perfect)
>
>
>In article <cg7g0h$1uu6$1@digitaldaemon.com>, h3r3tic says...
>>
>>Martin wrote:
>>> I works perfectly in valgrind.
>>> I tried 200 runs in valgrind, 0 errors.
>>> I tried 200 runs without valgrind, got 14 crahses.
>>> 
>>> What do I do?
>>
>>Have you tried DMD 0.100 ?
>
>

What caused the error, what did you change?
I mean, is the error really gone or is it just masked,
because the error was quite clever, it only came out only on some cases on some
computers. (And doing some not so big changes in this code made the error go
away)

I am asking because I want to know if I shlould relax or do more testing?


In article <cg8brq$2d3n$1@digitaldaemon.com>, Martin says...
>
>NOW INT FORKS FINE. thank you Walter, thank you all!
>
>For a second, I was afraid, that I need to move back to C.
>(Ok, there are always ways to workaround bugs, but when my program has to work
>correctly atleast 99.9998% of times that it's executed, then I am glad, that
>this bug is fixed)
>
>My job is to write a cgi web application and it was my personal choice to use D for it. So you know why i was so nervous.
>
>Ok, now I will continue with my project my deadline is coming very fast.
>D is a very good language for writing web (a lot better than PHP, or Java, or
>even better than C).
>So I reccomend it for that use.
>(Hopefully there are no more big bugs, but even when there are, hope they can be
>fixed. I have even seen some bugs in GNU C, so nothing is perfect)
>
>
>In article <cg7g0h$1uu6$1@digitaldaemon.com>, h3r3tic says...
>>
>>Martin wrote:
>>> I works perfectly in valgrind.
>>> I tried 200 runs in valgrind, 0 errors.
>>> I tried 200 runs without valgrind, got 14 crahses.
>>> 
>>> What do I do?
>>
>>Have you tried DMD 0.100 ?
>
>

<shameless plug>
Depending on what you're doing, you might find the Mango Tree could help out
rather a lot. It has an HTTP server, a Java-style servlet engine, an HTTP
client, Uri, Cookies, clustering, blah blah blah.
</shameless plug>

Nice to see D being used in what appears to be a commercial setting; although I imagine that might raise a few eyebrows at this point, being pre-release and all ... good for you!

<g>


"Martin" <Martin_member@pathlink.com> wrote in message news:cg8brq$2d3n$1@digitaldaemon.com...
> NOW INT FORKS FINE. thank you Walter, thank you all!
>
> For a second, I was afraid, that I need to move back to C.
> (Ok, there are always ways to workaround bugs, but when my program has to
work
> correctly atleast 99.9998% of times that it's executed, then I am glad,
that
> this bug is fixed)
>
> My job is to write a cgi web application and it was my personal choice to
use D
> for it. So you know why i was so nervous.
>
> Ok, now I will continue with my project my deadline is coming very fast. D is a very good language for writing web (a lot better than PHP, or Java,
or
> even better than C).
> So I reccomend it for that use.
> (Hopefully there are no more big bugs, but even when there are, hope they
can be
> fixed. I have even seen some bugs in GNU C, so nothing is perfect)
>
>
> In article <cg7g0h$1uu6$1@digitaldaemon.com>, h3r3tic says...
> >
> >Martin wrote:
> >> I works perfectly in valgrind.
> >> I tried 200 runs in valgrind, 0 errors.
> >> I tried 200 runs without valgrind, got 14 crahses.
> >>
> >> What do I do?
> >
> >Have you tried DMD 0.100 ?
>
>

"Martin" <Martin_member@pathlink.com> wrote in message news:cg8ckl$2dj0$1@digitaldaemon.com...
> What caused the error, what did you change?
> I mean, is the error really gone or is it just masked,
> because the error was quite clever, it only came out only on some cases on
some
> computers. (And doing some not so big changes in this code made the error
go
> away)
>
> I am asking because I want to know if I shlould relax or do more testing?

See the last post from me in this thread: 8/20/2004 at 2:58 PM