Reading Output Of dump Command

We're migrating our software build environment to some different hardware. My job is to try to verify that the binaries built on the two systems are the same. The problem is, Any two binaries I build, even on the same system, have some differences. I've looked at the contents of the output libraries with strings, dis, dump, and elfdump. Only dump shows the differences. So now I need to determine if those differences that dump shows REALLY make a difference. Can anyone point me to someplace that explains how to read the output of the dump command? The differences are in the string table section of the dump.

Similar Messages

Cannot read the output from windows command.

Hello
I have the following classes
package cmd;
import java.io.IOException;
public class CMD {
    public CMD(){
        ProcessBuilder pb = new ProcessBuilder()
        .command("cmd.exe","/c","del *.*")
        .redirectErrorStream(false);
        Process p;
        try {
            p = pb.start();
            StreamGobbler errorGobbler = new StreamGobbler(p.getErrorStream(), "ERROR");
            // any output?
            StreamGobbler outputGobbler = new StreamGobbler(p.getInputStream(), "OUTPUT");
            // start gobblers
            outputGobbler.start();
            errorGobbler.start();
        } catch (IOException e) {
            // TODO Auto-generated catch block
        System.out.println("eee "+e.getMessage());;
    public static void main(String[] args) {
        System.out.println("x");
        new CMD();
        System.out.println("x");
and
package cmd;
import java.io.BufferedReader;
import java.io.IOException;
import java.io.InputStream;
import java.io.InputStreamReader;
public class StreamGobbler extends Thread {
    InputStream is;
    String type;
    StreamGobbler(InputStream is, String type) {
        this.is = is;
        this.type = type;
    @Override
    public void run() {
        try {
            InputStreamReader isr = new InputStreamReader(is);
            BufferedReader br = new BufferedReader(isr);
            String line = null;
            while ((line = br.readLine()) != null)
                System.out.println(type + "> " + line);
        catch (IOException ioe) {
            ioe.printStackTrace();
Please note that I cannot seee the output from wndows command : del *.* and the java class execution does not finished.
I I will replace the above command with the dir command then the output of the command is visible.
Would you give me a hint about how to modify the above clases in order to parse the output of the del *.* ?
Please note that the above example is important because I am developping a tool and it is mandatory for that tool to parse the output from a windows batch command.
Best regards,

Please note that I cannot seee the output from wndows command : del *.* and the java class execution does not finished.
I I will replace the above command with the dir command then the output of the command is visible.
Would you give me a hint about how to modify the above clases in order to parse the output of the del *.* ?
No - but I will give you a hint about ProcessBuilder and how to develop software properly.
Hint #1: Don't try to automate something that you don't know, or understand, how to do manually.
a. Do you know how to execute 'del *.*' manually in a command window?
b. Did you try that manually to see what happens?
My guess is 'no'. If you had you would know that the response to a 'del *.*' command is going to be this:
Are you sure (Y/N)?
And your 'java class execution' doesn't finish because the 'del' command is waiting for you to answer that question.
Hint #2: Don't try to use ProcessBuilder for an application that requires console input unless you first know how to provide that console input via your Java code.
Your code will wait forever since it does NOT answer that question.
Search the net and The Java Tutorials and you can find examples of executing command line utilities. Then try those examples first and make sure that:
1. They work for you
2. You understand HOW they work
Then you can modify those examples to do what you want to do.

Problem with output string to command

hey i have no idea why this aint working
its a simple output string to command.
what it is supposed to do is make a new directory given by the input string
e.g. mkdir /home/luke/dep
thanks for the help
//methods input save files
     saveFile = JOptionPane.showInputDialog("Save Files To : ");
     //method command for saving files
     //Stream to write file
     FileOutputStream fout;
     try { Process myProcess = Runtime.getRuntime().exec("mkdir" + saveFile );
      InputStreamReader myIStreamReader = new InputStreamReader(myProcess.getInputStream());
      fout = new FileOutputStream ("file.txt");
      while ((ch = myIStreamReader.read()) != -1) { new PrintStream(fout).print((char)ch); } }
          catch (IOException anIOException) { System.out.println(anIOException); }

What you fail to understand is that "aint working" and "Problem with output string to command" tells us absolutely squat about what your problem is. This is the same as saying to the doctor "I'm sick" and expecting him to cure you. As mentioned by Enceph you need to provide details. Do you get error messages? If so post the entire error and indicate the line of code it occurs on. Do you get incorrect output? Then post what output you get, what output you expect. The more effort you put into your question the more effort others will put in their replies. So until you can manage to execute a little common sense then the only responses you will get will be flames. Now is your tiny little brain able to comprehend that?

Save output of a command

Hi all,
I am trying to save the output of a command so I can read it and decide weather it completed successfully or not. I am having trouble running the command though. It's working but the switches aren't.
$Servers = Get-Content Servers.txt | Sort-Object
ForEach ( $Server in $Servers ) {
& PsExec.exe \\$Server 'C:\Program Files (x86)\progfolder\program.exe' option -t=$Duration -e=$email -c=$Comment -q=110
When ran it complains I am not specifying any options/switches. Ideas?
Thanks.

Psexec can be very finicky with optional switches for the command you are trying to run through it.
Try this and let me know if it works:
$Servers = Get-Content Servers.txt | Sort-Object
ForEach ( $Server in $Servers ) {
& PsExec.exe \\$Server 'C:\Program Files (x86)\progfolder\program.exe' 'option -t=$Duration -e=$email -c=$Comment -q=110'
Boe Prox
Blog |
Twitter
PoshWSUS |
PoshPAIG | PoshChat |
PoshEventUI
PowerShell Deep Dives Book

Gnome Panel applet that shows output of system command.

Hi all;
Because of the recent hostile takeover of #archlinux channel by tilling WM fanatics.. I will ask here..
Does any one know of a Gnome Panel applet that shows the output of system command of your choice?
For people who Conky is a bit too much and they only want a simple piece of data available (like what is the current IP on ppp0 interface) like me.. this is a necessity.
If its not in existence I would probably make one.. shouldn't take long, I also would like to hear if there is any interest.
Thanks

That's exactly what I was looking for! Thank you!
Changed code to:
$dism = "X:\Windows\System32\Cmd.exe /c start CMD /k dism /apply-image /imagefile:D:\W7x86.wim /index:1 /applydir:C:\"
And voila, new window opened with the live output of dism.
new... and have a glazed over look about my eyes to prove it...

Using subprocess in python3 to get output of a command

Hi Friends. I am writing a python3 script for audacious to check the internet for album cover of the current playing song and then display it in conky. I am trying to call a command from python and get it's output:
audtool current-song-tuple-data album
but when i use this command in python like this:
subprocess.check_output(["audtool", "current-song-tuple-data album"])
i get the following error:
Unknown command "current-song-tuple-data album". Try "audtool help".
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File "/usr/lib/python3.2/subprocess.py", line 522, in check_output
raise CalledProcessError(retcode, cmd, output=output)
subprocess.CalledProcessError: Command '['audtool', 'current-song-tuple-data album']' returned non-zero exit status 1
Please , python experts on this forum, help me.

@Pranavg1890: Please add solved to your thread title then.
BTW: I found pexpect a good option for interacting with shell commands:
http://sourceforge.net/projects/pexpect/
It provides an easy way to deal with console output and react on certain patterns.

Sysql - use SQL queries against output of linux commands

Hello!
Many linux commands have table-like output. Sometimes it is better to analyze such output as a real table in relational database. I have published prototype of utility that parses output of one or several linux commands, saves it in database and allows to make SQL queries to that data. Program is written on python and uses sqlite database engine.
sysql at AUR
sysql at Github
Here is why I wrote it:
* No need to remember command syntax to format command output - just select necessary fields in SQL query
* No need to know sed, awk, head, join and other linux commands to manipulate with output - it's all SQLite
* Table data is stored with meaningful column name and type (int, text, float, datetime etc)
* All power of SQL can be used to query output (JOIN, WHERE, GROUP BY etc.)
* To support new command, output parser must be developed only once and then can be shared with community to make life easier
* All supported commands are kept in one place as set of python files, so it is easy to find out how to customize existing parsers or create new ones
This is my first community contribution, so kindly ask everyone to share your opinions and advices on what can be done better. Thank you!
Examples:
Display help and list of available commands:
sysql
Display output of ps command:
sysql ps
Query output of lsblk command:
sysql -q "SELECT device,uuid,filesystem FROM lsblk" lsblk
Query output of several commands:
sysql -q "SELECT ps.pid, ps.command, ps.elapsed_time, lsof.name FROM ps JOIN lsof ON ps.pid = lsof.pid WHERE name LIKE '%LISTEN%'" ps -e --- lsof -Pni4

I am not sure, if I will ever use it, but I do think, this is an _amazing_ idea!
You may consider something like a global repository for output parsers accessable directly via sysql.
Last edited by myname (2013-11-24 09:16:59)

Using VI Example Basic Serial Write Read to send AT commands to Cell phone modem error 1073807360

I am using the NI Example VI: Basic Serial Write and Read to send AT commands to a Cell phone acting as a Modem. I can send AT commands to this phone using Hyperterm when I select the modem driver by name in the hypert port selection field but not as com 7 which it occupies according to device manager modem properties. The basic serial vi does not show the modem driver as a selection, only ports by comX are shown. I get error 1073807360.

Have you tried to put the name you enter in Hyperterminal in the VISA resource control? If Com 7 doesn't show, you can simply type "COM 7" in the VISA resource control. Or use "ASRL::INSTR 7".
Also, make sure the connection in hyperterminal is closed, before you open the port in LabVIEW.
Hope it helps,
Wiebe.

I have a Windows 8.1 machine. I used a projecteor a while back in a Power Point presentation. Now my menus for Adobe are very small and hard to read. The print command is so compressed that I cannot read or use it. How do I fix this problem?

I used a projecteor a while back in a Power Point presentation. Now my menus for Adobe are very small and hard to read. The print command is so compressed that I cannot read or use it. How do I fix this problem?

There is no application called "Adobe" - you are either working with Adobe Acrobat or the free Adobe Reader. Open up the preferences for the application (Edit>Preferences), then go to the "General" category and modify the settings for "Scale for screen resolution". You will have to restart the application after you do that. Does that fix your problems?

Make System.in read input from a command prompt

How can i make System.in read input from a command prompt which is opened after program
is started. Please note that program starts without commad promt. Can u plz help?
sharmila

System.in DOES read from the command shell that you start the app in.
What you don't have is a prompt.
You should know about Java Almanac. There are code samples for simple things like I/O that everyone should know about. There's an example there to help you.
MOD

"Reader Extensions ES" in Command Prompt.

Is it possible to use the "Reader Extensions ES" through command prompt. Kindly advice me.
Thanks,
Prabudass

Ah, this is the first mention you have made of an Adobe product. Now,
LiveCycle Designer does not open in a browser, so I assume you are
doing one of these
* Opening Acrobat in a browser
* Opening Adobe Reader in a browser
* Opening a preview in Designer
* Something else?
If you can describe in detail what you are doing with Adobe products
it may help to focus. HOWEVER, you have added to message topics which
seem to have NOTHING to do with your question. Does your question
connect to "Reader Extensions ES in Command Prompt" in some way that
isn't clear? If not, please post ONE new message with a suitable title
in the specific forum for the Adobe product involved. Thanks and good
luck,
Aandi Inston

Posttriggered DAQmx Read output if no trigger received.

I am running a posttriggered analog voltage input on a PCIe-6251 via DAQmx and I need to know what voltage Labview bins if no posttrigger is received and I set the timeout response to "cancel error on match."

MikeK,
I am not sure what you mean by post-triggered. Are you referring to a reference trigger, which keeps a buffer of data so that after it is triggered that buffer of data can still be recorded?
Please attach a snippet of code.
If you are in fact using a reference trigger and the DAQmx Read times out and the error is ignored by your error handler, no voltage data should be recorded. If you have this running, you can easily test this by creating an indicator on your DAQmx Read output and verifying that nothing is recorded.
Best.
Joey S.
Software Product Manager
National Instruments

Script hangs when reading output of command inside vbscript

Following code hangs after the line "4 Go" but only on windows 2003.
Set objShell = CreateObject("WScript.Shell")
wscript.echo "2 Go"
backupstate = "wmic PATH WIN32_SERVICE where (name='vss') GET state"
wscript.echo "3 Go"
Set objExecObject = objShell.Exec(backupstate)
wscript.echo "4 Go"
With objExecObject
Do While .Status=0
Wscript.Sleep 10
Do While Not .StdOut.AtEndOfStream
strText = .StdOut.ReadLine()
If Not .StdErr.AtEndOfStream Then
.StdErr.ReadLine
End If
Loop
Loop
End With
Same code works perfectly fine on Windows 2008 and above.
Any suggestion?
-KAKA-

Your script hangs (or more precisely: it keeps looping) because the Exec method of of the Shell object is notoriously unreliable when it comes to detecting the status of the executable it invokes. You can easily find out by placing the line
wscript.echo "Status=" & objExecObject.status
inside your loop. This only works properly if you run the script with cscript.exe.
As Frederik says. :)
To explicitly answer why that MSKB article suggests continually emptying the error buffer, it's because doing so is better than
not doing so.
Another workaround I use in preference to embedding the console tool within a WSH script is to factor out the tool so I don't have to manipulate it internally; instead I pipe the output in to the script.
For example, suppose your script is named ProcessWmicOutput.vbs. within the script you would do something like this:
data = WScript.Stdin.ReadAll
to get all the data from wmic into a variable named data . Alternatively, you would do something like this, line by line (I'm making the script just relay StdOut from wmic):
Do While Not WScript.StdIn.AtEndOfStream
WScript.StdOut.WriteLine WScript.StdIn.ReadLine()
Loop
To run the script, getting wmic data, you would do this at a command prompt:
wmic PATH WIN32_SERVICE where (name='vss') GET state | cscript ProcessWmicOutput.vbs

Process.Start - getting different output when running command using this method than I am if I run same command in CMD prompt

Hi
Creating an application to analyze .dmp files - all working well except this odd issue
If I open command prompt and enter this command:-
kd -z C:\Windows\MiniDump\042414-24632-01.dmp -c "!analyze -v"
Then it works and shows me all the output I need (shown at bottom of post)
If I run same command in VB.net using following code - then it doesn't give the same output - the bits I need at the end created by the !analyze -v switch don't appear
Any ideas why it is not seeing the switch correctly - setting a breakpoint and checking contents of startinfo seems to be showing correct cmd line i.e. "kd -z C:\windows\minidump\042414-24632-01.dmp -c "!analyze –v;q""
Dim myprocess As New Process()
myprocess.StartInfo.FileName = "C:\Program Files (x86)\Windows Kits\8.1\Debuggers\x86\kd"
myprocess.StartInfo.Arguments = "-z C:\windows\minidump\042414-24632-01.dmp -c ""!analyze –v;q"""
myprocess.StartInfo.UseShellExecute = False
myprocess.StartInfo.RedirectStandardOutput = True
myprocess.StartInfo.CreateNoWindow = True
myprocess.Start()
TextBox1.AppendText(myprocess.StandardOutput.ReadToEnd())
Output when run from cmd prompt:-
C:\Program Files (x86)\Windows Kits\8.1\Debuggers\x86>kd -z C:\Windows\MiniDump\042414-24632-01.dmp -c "!analyze -v;q"
Microsoft (R) Windows Debugger Version 6.3.9600.17298 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\MiniDump\042414-24632-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: *** Invalid ***
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
Executable search path is:
* Symbols can not be loaded because symbol path is not initialized. *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18205.x86fre.win7sp1_gdr.130708-1532
Machine Name:
Kernel base = 0x82e3e000 PsLoadedModuleList = 0x82f874d0
Debug session time: Thu Apr 24 13:36:18.672 2014 (UTC + 1:00)
System Uptime: 0 days 0:00:38.703
* Symbols can not be loaded because symbol path is not initialized. *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
************* Symbol Loading Error Summary **************
Module name Error
ntkrnlpa The system cannot find the file specified
You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the
command that caused symbols to be loaded.
You should also verify that your symbol search path (.sympath) is correct.
* Bugcheck Analysis *
Use !analyze -v to get detailed debugging information.
BugCheck 50, {afa99150, 0, 88c557d7, 0}
*** WARNING: Unable to verify timestamp for mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
*** WARNING: Unable to verify timestamp for mfehidk.sys
*** ERROR: Module load completed but symbols could not be loaded for mfehidk.sys
*** WARNING: Unable to verify timestamp for HipShieldK.sys
*** ERROR: Module load completed but symbols could not be loaded for HipShieldK.sys
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: nt!_KPRCB ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: nt!_KPRCB ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: nt!_KPRCB ***
Probably caused by : mfehidk.sys ( mfehidk+377d7 )
Followup: MachineOwner
1: kd> kd: Reading initial command '!analyze -v;q'
* Bugcheck Analysis *
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced. This cannot be protected by try-except,
it must be protected by a Probe. Typically the address is just plain bad or it
is pointing at freed memory.
Arguments:
Arg1: afa99150, memory referenced.
Arg2: 00000000, value 0 = read operation, 1 = write operation.
Arg3: 88c557d7, If non-zero, the instruction address which referenced the bad memory
address.
Arg4: 00000000, (reserved)
Debugging Details:
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: nt!_KPRCB ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: nt!_KPRCB ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: nt!_KPRCB ***
ADDITIONAL_DEBUG_TEXT:
You can run '.symfix; .reload' to try to fix the symbol path and load symbols.
MODULE_NAME: mfehidk
FAULTING_MODULE: 82e3e000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 4d2e1e3e
READ_ADDRESS: GetPointerFromAddress: unable to read from 00000000
GetPointerFromAddress: unable to read from 00000000
unable to get nt!MmSpecialPoolStart
unable to get nt!MmSpecialPoolEnd
unable to get nt!MmPagedPoolEnd
unable to get nt!MmNonPagedPoolStart
unable to get nt!MmSizeOfNonPagedPoolInBytes
afa99150
FAULTING_IP:
mfehidk+377d7
88c557d7 0fb70c06 movzx ecx,word ptr [esi+eax]
MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: WIN7_DRIVER_FAULT
BUGCHECK_STR: 0x50
CURRENT_IRQL: 0
ANALYSIS_VERSION: 6.3.9600.17298 (debuggers(dbg).141024-1500) x86fre
LAST_CONTROL_TRANSFER: from 82e7eaa8 to 82ecb879
STACK_TEXT:
WARNING: Stack unwind information not available. Following frames may be wrong.
ad0baf90 82e7eaa8 00000000 afa99150 00000000 nt+0x8d879
ad0bafa8 88c557d7 badb0d00 00000000 88c4ceb0 nt+0x40aa8
ad0bb040 88c4f97d 001a99b0 afa91000 00000000 mfehidk+0x377d7
ad0bb090 88c52b16 00770220 ad0bb0fc 00000010 mfehidk+0x3197d
ad0bb0bc 98d5fb73 ae770220 ad0bb0fc 00000010 mfehidk+0x34b16
ad0bb140 98d5fc43 ae738c30 98d6b62a aace7220 HipShieldK+0xb73
ad0bb168 98d6b882 ad0bb19c 00000000 98d77b44 HipShieldK+0xc43
ad0bb1b8 98d631a9 00000bd4 0000102c ad0bb208 HipShieldK+0xc882
ad0bb330 88c47795 00000bd4 0000102c ad0bb401 HipShieldK+0x41a9
ad0bb400 88c22b57 0000102c ad0bb460 85b3dee0 mfehidk+0x29795
ad0bb41c 88c232c6 ad0bb430 0000000c 8c4b6ce0 mfehidk+0x4b57
ad0bb43c 830a5acb adb6b9b8 0000102c ad0bb460 mfehidk+0x52c6
ad0bb4f4 830adaf8 adb16030 01b6b9b8 ad0bb550 nt+0x267acb
ad0bbc00 82e7b8c6 038ae710 038ae6ec 02000000 nt+0x26faf8
ad0bbc34 77a470f4 badb0d00 038ae3dc 00000000 nt+0x3d8c6
ad0bbc38 badb0d00 038ae3dc 00000000 00000000 0x77a470f4
ad0bbc3c 038ae3dc 00000000 00000000 00000000 0xbadb0d00
ad0bbc40 00000000 00000000 00000000 00000000 0x38ae3dc
STACK_COMMAND: kb
FOLLOWUP_IP:
mfehidk+377d7
88c557d7 0fb70c06 movzx ecx,word ptr [esi+eax]
SYMBOL_STACK_INDEX: 2
SYMBOL_NAME: mfehidk+377d7
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: mfehidk.sys
BUCKET_ID: WRONG_SYMBOLS
FAILURE_BUCKET_ID: WRONG_SYMBOLS
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:wrong_symbols
FAILURE_ID_HASH: {70b057e8-2462-896f-28e7-ac72d4d365f8}
Followup: MachineOwner
quit:
output when run in my app:-
Microsoft (R) Windows Debugger Version 6.3.9600.17298 X86
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Windows\MiniDump\042414-24632-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available
Symbol search path is: *** Invalid ***
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
Executable search path is:
* Symbols can not be loaded because symbol path is not initialized. *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (4 procs) Free x86 compatible
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 7601.18205.x86fre.win7sp1_gdr.130708-1532
Machine Name:
Kernel base = 0x82e3e000 PsLoadedModuleList = 0x82f874d0
Debug session time: Thu Apr 24 13:36:18.672 2014 (UTC + 1:00)
System Uptime: 0 days 0:00:38.703
* Symbols can not be loaded because symbol path is not initialized. *
* The Symbol Path can be set by: *
* using the _NT_SYMBOL_PATH environment variable. *
* using the -y <symbol_path> argument when starting the debugger. *
* using .sympath and .sympath+ *
Unable to load image \SystemRoot\system32\ntkrnlpa.exe, Win32 error 0n2
*** WARNING: Unable to verify timestamp for ntkrnlpa.exe
*** ERROR: Module load completed but symbols could not be loaded for ntkrnlpa.exe
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
************* Symbol Loading Error Summary **************
Module name Error
ntkrnlpa The system cannot find the file specified
You can troubleshoot most symbol related issues by turning on symbol loading diagnostics (!sym noisy) and repeating the
command that caused symbols to be loaded.
You should also verify that your symbol search path (.sympath) is correct.
* Bugcheck Analysis *
Use !analyze -v to get detailed debugging information.
BugCheck 50, {afa99150, 0, 88c557d7, 0}
*** WARNING: Unable to verify timestamp for mssmbios.sys
*** ERROR: Module load completed but symbols could not be loaded for mssmbios.sys
*** WARNING: Unable to verify timestamp for mfehidk.sys
*** ERROR: Module load completed but symbols could not be loaded for mfehidk.sys
*** WARNING: Unable to verify timestamp for HipShieldK.sys
*** ERROR: Module load completed but symbols could not be loaded for HipShieldK.sys
***** Kernel symbols are WRONG. Please fix symbols to do analysis.
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: nt!_KPRCB ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: nt!_KPRCB ***
*** Either you specified an unqualified symbol, or your debugger ***
*** doesn't have full symbol information. Unqualified symbol ***
*** resolution is turned off by default. Please either specify a ***
*** fully qualified symbol module!symbolname, or enable resolution ***
*** of unqualified symbols by typing ".symopt- 100". Note that ***
*** enabling unqualified symbol resolution with network symbol ***
*** server shares in the symbol path may cause the debugger to ***
*** appear to hang for long periods of time when an incorrect ***
*** symbol name is typed or the network symbol server is down. ***
*** For some commands to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** Type referenced: nt!_KPRCB ***
Probably caused by : mfehidk.sys ( mfehidk+377d7 )
Followup: MachineOwner
Darren Rose

Try it by opening the Cmd prompt as the actual process and passing the Filename and its arguments as the arguments of the Cmd process. If you notice there is a "-C" before the Filename and Arguments in this example. The "-C"
tells the cmd to execute the commands and then close itself. You can also use a "-K" which tells the cmd to execute the commands and keep itself open. Being you are not showing the cmd window you don`t want to keep it opened because the
user can`t close it so, that is why i used "-C".
I don`t have the program so, you can just experiment to see what it does. Maybe you should try using "-K" and show the cmd window by commenting out the CreateNoWindow line so you can see what is in the cmd window while testing.
Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button1.Click
Dim filepath As String = """C:\Program Files (x86)\Windows Kits\8.1\Debuggers\x86\kd"""
Dim args As String = " -z C:\windows\minidump\042414-24632-01.dmp -c ""!analyze –v;q"""
Dim p As New Process
With p.StartInfo
.FileName = "cmd.exe"
.Arguments = "-c " & filepath & args
.UseShellExecute = False
.CreateNoWindow = True
.RedirectStandardOutput = True
End With
p.Start()
TextBox1.Text = p.StandardOutput.ReadToEnd
End Sub
If you say it can`t be done then i`ll try it

How do I show the output of a command called within a gui script

I'm starting from scratch on a project I've been tasked with. My intention is a quick down-and-dirty way to apply an image within winPE to apply a windows image to the machine I've booted to a usb drive loaded with winPE.
Here's my start. It's rough, but, I have to start somewhere.
[void] [System.Reflection.Assembly]::LoadWithPartialName("System.Windows.Forms")
[void] [System.Reflection.Assembly]::LoadWithPartialName("System.Drawing")
$objForm = New-Object System.Windows.Forms.Form
$objForm.Text = "DISM"
$objForm.Size = New-Object System.Drawing.Size(600,400)
$objForm.AutoSizeMode = "GrowAndShrink"
$objForm.StartPosition = "CenterScreen"
$objForm.FormBorderStyle = "Fixed3D"
$objForm.KeyPreview = $True
Function do_DISM{
$dism = "dism /apply-image /imagefile:D:\W7x86.wim /index:1 /applydir:C:\"
Invoke-Expression $dism
$DISMButton = New-Object System.Windows.Forms.Button
$DISMButton.BackColor = "ButtonFace"
$DISMButton.Location = New-Object System.Drawing.Size(12,27)
$DISMButton.Size = New-Object System.Drawing.Size(120,25)
$DISMButton.TabIndex = 1
$DISMButton.Text = “Start DISM”
$DISMButton.Add_Click({do_DISM})
$objForm.Controls.Add($DISMButton)
$objForm.Add_Shown({$objForm.Activate()})
[void] $objForm.ShowDialog()
Now, this does work, and it will in fact apply the windows image to c:\ which is what I need it to do. But, I have a few quesitons.
Am I correct to use "Invoke-Expression" in the function do_DISM to start the command? According to technet's articles, yes, but, want to make sure I'm doing this the proper way, since I'm learning that calling Invoke-Expression isn't always
the way to do things.
Also, since this will be used by others in my group, I'm going to need to show some sort of progress report on how far along DISM is getting along, otherwise, 5 minutes into DISM running, some people are going to think nothing's happening, and just power
down the computer no matter what I tell them. I know that running DISM from the command line, it will show a progress bar that is adequate for what I'm needing. Running the script above and clicking the button, it does run, but, all in the background
with no progress indication. Is there a way I can tell either in the function or when the function calls Invoke-Expression to run DISM, to open in a new command window which shows the live progress of the command running?
Again, my disclaimer: VERY new to writing bits of code, and am trying my best here, so, thanks in advance for patience with me.

That's exactly what I was looking for! Thank you!
Changed code to:
$dism = "X:\Windows\System32\Cmd.exe /c start CMD /k dism /apply-image /imagefile:D:\W7x86.wim /index:1 /applydir:C:\"
And voila, new window opened with the live output of dism.
new... and have a glazed over look about my eyes to prove it...

Reading Output Of dump Command

Similar Messages

Maybe you are looking for