small memory dump or kernel memory dump?

[Dany]

Hello,
I have a doubt about Windows memory dumps for crash debugging. Do you
suggest to set small memory dump or kernel memory dump?

Thank you
Daniel

 

[Andrew Rossmann]

I have a doubt about Windows memory dumps for crash debugging. Do you
suggest to set small memory dump or kernel memory dump?

Unless you are a programmer, there is no need for the dumps. Set it to
none.

 

[Yousuf Khan]

Hello,
I have a doubt about Windows memory dumps for crash debugging. Do you
suggest to set small memory dump or kernel memory dump?

I'd suggest using the small memory dump rather than the full one. You
can use programs like BlueScreenView to analyse them afterwards, and
they only require the small dumps. If the problems persist and requires
more information, then usually Microsoft will ask you to turn on the
full memory dumps.

http://www.nirsoft.net/utils/blue_screen_view.html

I don't agree at all with the other posting suggesting you turn them off
altogether. First of all, if you're not having any problems, then you
won't be wasting any space storing these dumps anyways. But once you do
have a problem, it's good to have these tools already in place.

Yousuf Khan

 

[Dany]

Unless you are a programmer, there is no need for the dumps. Set it to
none.

I am a programmer...
But what happens if system stops unexpectedly and I set it to none? Will
I get the information about crash?

Thank you
Daniel

 

[Dany]

I'd suggest using the small memory dump rather than the full one. You
can use programs like BlueScreenView to analyse them afterwards, and
they only require the small dumps. If the problems persist and
requires more information, then usually Microsoft will ask you to turn
on the full memory dumps.

I don't agree at all with the other posting suggesting you turn them
off altogether. First of all, if you're not having any problems, then
you won't be wasting any space storing these dumps anyways. But once
you do have a problem, it's good to have these tools already in place.

Yousuf Khan

Thank you Yousuf!
Daniel

 

[Vic RR Garcia]

I am a programmer...
But what happens if system stops unexpectedly and I set it to none? Will
I get the information about crash?

Clearly, you are NOT a programmer.
No real programmer will have to ask those 2 questions.

 

[Yousuf Khan]

I am a programmer...
But what happens if system stops unexpectedly and I set it to none? Will
I get the information about crash?

Some information may come back to you through the Event Viewer after the
crash, but not nearly as much as you'd get with a core dump present. And
if the problem is severe enough, you may find yourself in an endless
reboot cycle, and you'll never be able to get to the Event Viewer
anyways. If you have crash dumps enabled, then you can copy them to
another system by booting into Linux on a CD, and analyse them on a
remote system.

Yousuf Khan

 

[Dany]

Clearly, you are NOT a programmer.
No real programmer will have to ask those 2 questions.

Every human being can have doubts.

I am a simple programmer, who makes non-GUI programs, currently.

D.

 

[Dany]

Some information may come back to you through the Event Viewer after
the
crash, but not nearly as much as you'd get with a core dump present.
And if the problem is severe enough, you may find yourself in an
endless reboot cycle, and you'll never be able to get to the Event
Viewer anyways. If you have crash dumps enabled, then you can copy
them to another system by booting into Linux on a CD, and analyse them
on a remote system.

Thank you for the suggestion
D.

 

[Stephen Wolstenholme]

Unless you are a programmer, there is no need for the dumps. Set it to
none.

Dump cracking and programming are not that closely related. In my many
years of dump cracking the only time I needed to get into programming
was when I needed to explain what was wrong to a programmer.
Programming faults rarely causes dumps.

Steve

--
Neural network applications, help and support.

Neural Network Software. www.npsl1.com
EasyNN-plus. Neural Networks plus. www.easynn.com
SwingNN. Forecast with Neural Networks. www.swingnn.com
JustNN. Just Neural Networks. www.justnn.com

 

[Ed Cryer]

Dump cracking and programming are not that closely related. In my many
years of dump cracking the only time I needed to get into programming
was when I needed to explain what was wrong to a programmer.
Programming faults rarely causes dumps.

Steve

I used to work as an applications programmer on old mainframes. We had a
whole team of systems programmers for support; they were working hand in
hand with ICL in a large government computer centre. We used to go to
them when we found problems that we couldn't explain. One of them was
called "Run-it-again Ken". We used to try and bypss him.

Ed

 

[Stephen Wolstenholme]

I used to work as an applications programmer on old mainframes. We had a
whole team of systems programmers for support; they were working hand in
hand with ICL in a large government computer centre. We used to go to
them when we found problems that we couldn't explain. One of them was
called "Run-it-again Ken". We used to try and bypss him.

Ed

Hello,

I worked on VME and mainframe development for about 20 years at West
Gorton but I can't remember any support people called Ken. Where was
he based?

Steve


--
Neural network applications, help and support.

Neural Network Software. www.npsl1.com
EasyNN-plus. Neural Networks plus. www.easynn.com
SwingNN. Forecast with Neural Networks. www.swingnn.com
JustNN. Just Neural Networks. www.justnn.com

 

[Allen]

Clearly, you are NOT a programmer.
No real programmer will have to ask those 2 questions.

Goodbye, Vic Railroad Garcia. THIS NG IS NOT LIMITED TO PROGRAMMERS.
Repeat: THIS NG IS NOT LIMITED TO PROGRAMMERS.
Allen

 

[Gene E. Bloch]

Programming faults rarely causes dumps.

I guess you lack my talents

 

[Ed Cryer]

Hello,

I worked on VME and mainframe development for about 20 years at West
Gorton but I can't remember any support people called Ken. Where was
he based?

Steve

In Hastings with the old DOE, back in the 80s.

Ed

 

[Brian Gregory [UK]]

Clearly, you are NOT a programmer.
No real programmer will have to ask those 2 questions.

You don't count BASIC programmers, Perl programmers, Linux programmers,
programmers that are new to Windows, or ARM based embedded system
programmers then?

 

[Char Jackson]

You don't count BASIC programmers, Perl programmers, Linux programmers,
programmers that are new to Windows, or ARM based embedded system
programmers then?

If I were being argumentative, I'd categorize that last set as
follows:

BASIC programmers - "BASIC programming" is sort of an oxymoron
Perl programmers - more of a scripting language than programming
Linux programmers - not programming, Linux is an OS
programmers that are new to Windows - not a programming language
ARM based embedded system programmers - judging by the weakness of the
four above, this one probably doesn't qualify, either.

 

[Gene E. Bloch]

If I were being argumentative, I'd categorize that last set as
follows:

BASIC programmers - "BASIC programming" is sort of an oxymoron
Perl programmers - more of a scripting language than programming
Linux programmers - not programming, Linux is an OS
programmers that are new to Windows - not a programming language
ARM based embedded system programmers - judging by the weakness of the
four above, this one probably doesn't qualify, either.

I *really* hope you mean that smiley

 

[Char Jackson]

I *really* hope you mean that smiley

I do, but I don't think I'm wrong.

 

[Gene E. Bloch]

On Fri, 2 Sep 2011 00:28:31 +0100, "Brian Gregory [UK]"

On 8/31/2011 18:14, Dany wrote:



Unless you are a programmer, there is no need for the dumps. Set it to
none.

I am a programmer...
But what happens if system stops unexpectedly and I set it to none? Will
I get the information about crash?

Clearly, you are NOT a programmer.
No real programmer will have to ask those 2 questions.

You don't count BASIC programmers, Perl programmers, Linux programmers,
programmers that are new to Windows, or ARM based embedded system
programmers then?

If I were being argumentative, I'd categorize that last set as
follows:

BASIC programmers - "BASIC programming" is sort of an oxymoron
Perl programmers - more of a scripting language than programming
Linux programmers - not programming, Linux is an OS
programmers that are new to Windows - not a programming language
ARM based embedded system programmers - judging by the weakness of the
four above, this one probably doesn't qualify, either.

I *really* hope you mean that smiley

I do, but I don't think I'm wrong.

Well, both Linux and Windows are environments in which programmers can
create applications, and Basic is no longer the language whose complete
definition almost filled one side of an 8.5"x11" sheet of paper when I
first used it.

As far as scripts, batch files, makefiles, AWK, and such are concerned,
one can write real applications to do useful work in them, and it
requires serious thought and skills to accomplish some of those tasks.

You are entitled to your opinion, but it doesn't have to be correct

(Yeah, I know, you can apply the same aphorism to me!)