Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.clipper.visual-objects > #6696 > unrolled thread

Must have for all programmers

Started by"Arne Ortlinghaus" <Arne.Ortlinghaus@acs.it>
First post2014-03-21 18:19 +0100
Last post2014-03-25 08:53 -0500
Articles 2 — 2 participants

Back to article view | Back to comp.lang.clipper.visual-objects


Contents

  Must have for all programmers "Arne Ortlinghaus" <Arne.Ortlinghaus@acs.it> - 2014-03-21 18:19 +0100
    Re: Must have for all programmers "Willie Moore" <williem@wmconsulting.com> - 2014-03-25 08:53 -0500

#6696 — Must have for all programmers

From"Arne Ortlinghaus" <Arne.Ortlinghaus@acs.it>
Date2014-03-21 18:19 +0100
SubjectMust have for all programmers
Message-ID<lghsbq$6it$1@dont-email.me>
For me the following free programs from sysinternals.com are regularly 
important tools for looking into our or foreign Exe programs:

Process Explorer (Procexp.exe)
Tool for viewing all running programs showing open files and loaded dlls.
You can see more ressorces occupied by a program than with Task Manager and 
get also some more ideas what can slow down a whole computer.

Process Monitor (Procmon.exe)
Tool for seeing all file/registry/TCP access of a program.
If you have an own program or a foreign program that does not make something 
you can see as writing to a hidden logfile and then terminating without an 
error then you may find some hints what has done the program. Also useful 
for example when a program is searching for a file that does not exist or is 
corrupt. Important: You can crash the whole computer/server if you collect 
information for too much time. Just enable getting information for a short 
time. One of the last time I have used it successfully when having a Java 
program from Oracle which did not start without giving a message. But it 
wrote an error log file hidden deep in the order hierarchy from which I 
could find the reason.

Process Dump (Procdump.exe)
This is command line tool that generates a dump file when a program hangs, 
terminates or gets exceptions. You can start it hidden with your program and 
when the program crashes or terminates without a message a dump file is 
written automatically. You can open the dump file with Windbg.exe from the 
"Debugging Tools for Windows". There you can open the Call stack, probably 
click multiple times "Show more". If you are lucky you can see the stack 
trace with all methods/functions called before crashing. One of the last 
times I used it was to verify that when calling Microsoft Outlook from an 
own program that Outlook was the culprite and not my program.

Arne Ortlinghaus
ACS Data Systems 

[toc] | [next] | [standalone]


#6706

From"Willie Moore" <williem@wmconsulting.com>
Date2014-03-25 08:53 -0500
Message-ID<lgs1o7$4ag$1@speranza.aioe.org>
In reply to#6696
Arne,

I agree. I use the same programs.

Regards,
Willie
Vulcan VIP

"Arne Ortlinghaus"  wrote in message news:lghsbq$6it$1@dont-email.me...

For me the following free programs from sysinternals.com are regularly
important tools for looking into our or foreign Exe programs:

Process Explorer (Procexp.exe)
Tool for viewing all running programs showing open files and loaded dlls.
You can see more ressorces occupied by a program than with Task Manager and
get also some more ideas what can slow down a whole computer.

Process Monitor (Procmon.exe)
Tool for seeing all file/registry/TCP access of a program.
If you have an own program or a foreign program that does not make something
you can see as writing to a hidden logfile and then terminating without an
error then you may find some hints what has done the program. Also useful
for example when a program is searching for a file that does not exist or is
corrupt. Important: You can crash the whole computer/server if you collect
information for too much time. Just enable getting information for a short
time. One of the last time I have used it successfully when having a Java
program from Oracle which did not start without giving a message. But it
wrote an error log file hidden deep in the order hierarchy from which I
could find the reason.

Process Dump (Procdump.exe)
This is command line tool that generates a dump file when a program hangs,
terminates or gets exceptions. You can start it hidden with your program and
when the program crashes or terminates without a message a dump file is
written automatically. You can open the dump file with Windbg.exe from the
"Debugging Tools for Windows". There you can open the Call stack, probably
click multiple times "Show more". If you are lucky you can see the stack
trace with all methods/functions called before crashing. One of the last
times I used it was to verify that when calling Microsoft Outlook from an
own program that Outlook was the culprite and not my program.

Arne Ortlinghaus
ACS Data Systems 

[toc] | [prev] | [standalone]


Back to top | Article view | comp.lang.clipper.visual-objects


csiph-web