OpenJDK on FreeBSD: "Given reserved space must have been reserved already" - installation

I'm trying to get Artifactory up and running on a FreeBSD machine. I installed /usr/ports/devel/artifactory, seemingly without problem, and then ran "/usr/local/etc/rc.d/artifactory start". It said Artifactory was starting, and didn't give any obvious signs of error, but when the script ended, Artifactory was not running. I found that every time I do this, the following is appended to /usr/local/artifactory/logs/boot.log:
# A fatal error has been detected by the Java Runtime Environment:
#
# Internal Error (g1PageBasedVirtualSpace.cpp:54), pid=87801, tid=100176
# guarantee(rs.is_reserved()) failed: Given reserved space must have been reserved already.
Googling that "Given reserved space must have been reserved already" reveals no information that is particularly useful to me. It seems to be a message from within the OpenJDK.
The log file also mentions that another file was created with more detailed error information. That file has a stack trace and various other info:
--------------- T H R E A D ---------------
Current thread (0x29cb0800): JavaThread "Unknown thread" [_thread_in_vm, id=100176, stack(0xbf9be000,0xbf9fe000)]
Stack: [0xbf9be000,0xbf9fe000], sp=0xbf9fd528, free space=253k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
V [libjvm.so+0x8234ed] JVM_handle_bsd_signal+0x166bbd
V [libjvm.so+0x36ef3f] SUNWprivate_1.1+0x36ef3f
V [libjvm.so+0x40df4c] AsyncGetCallTrace+0x2c0bc
V [libjvm.so+0x40def4] AsyncGetCallTrace+0x2c064
V [libjvm.so+0x40ff0b] AsyncGetCallTrace+0x2e07b
V [libjvm.so+0x41017e] AsyncGetCallTrace+0x2e2ee
V [libjvm.so+0x3f5874] AsyncGetCallTrace+0x139e4
V [libjvm.so+0x7ea485] JVM_handle_bsd_signal+0x12db55
V [libjvm.so+0x7ea105] JVM_handle_bsd_signal+0x12d7d5
V [libjvm.so+0x471291] AsyncGetCallTrace+0x8f401
V [libjvm.so+0x7cccd3] JVM_handle_bsd_signal+0x1103a3
V [libjvm.so+0x4d0eeb] JNI_CreateJavaVM+0x6b
C [java+0x3c35] JavaMain+0x1d5
C [libthr.so.3+0x76dc] operator->+0x81c
C 0x00000000
--------------- P R O C E S S ---------------
Java Threads: ( => current thread )
Other Threads:
=>0x29cb0800 (exited) JavaThread "Unknown thread" [_thread_in_vm, id=100176, stack(0xbf9be000,0xbf9fe000)]
VM state:not at safepoint (not fully initialized)
VM Mutex/Monitor currently owned by a thread: ([mutex/lock_event])
[0x29c48640] Heap_lock - owner thread: 0x29cb0800
GC Heap History (0 events):
No events
Deoptimization events (0 events):
No events
Internal exceptions (0 events):
No events
Events (0 events):
No events
Dynamic libraries:
0x08048000 /usr/local/openjdk8/bin/java
0x2807d000 /lib/libz.so.6
0x28091000 /lib/libthr.so.3
0x280b3000 /lib/libc.so.7
0x28c00000 /usr/local/openjdk8/jre/lib/i386/server/libjvm.so
0x28237000 /lib/libm.so.5
0x2825d000 /usr/lib/libc++.so.1
0x2830c000 /lib/libcxxrt.so.1
0x28325000 /lib/libgcc_s.so.1
0x28331000 /usr/local/openjdk8/jre/lib/i386/libverify.so
0x2833d000 /usr/local/openjdk8/jre/lib/i386/libjava.so
0x2836a000 /usr/local/openjdk8/jre/lib/i386/libzip.so
0x28054000 /libexec/ld-elf.so.1
VM Arguments:
jvm_args: -Djava.util.logging.config.file=/usr/local/artifactory/tomcat/conf/logging.properties -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Xms512m -Xmx2g -Xss256k -XX:+UseG1GC -Djruby.compile.invokedynamic=false -Dfile.encoding=UTF8 -Dartdist=zip -Dartifactory.home=/usr/local/artifactory -Dfile.encoding=UTF8 -Djruby.compile.invokedynamic=false -Djava.endorsed.dirs=/usr/local/artifactory/tomcat/endorsed -Dcatalina.base=/usr/local/artifactory/tomcat -Dcatalina.home=/usr/local/artifactory/tomcat -Djava.io.tmpdir=/usr/local/artifactory/tomcat/temp
java_command: org.apache.catalina.startup.Bootstrap start
java_class_path (initial): /usr/local/artifactory/tomcat/bin/bootstrap.jar:/usr/local/artifactory/tomcat/bin/tomcat-juli.jar
Launcher Type: SUN_STANDARD
Environment Variables:
JAVA_HOME=/usr/local/openjdk8
PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/local/bin:/nonexistent/bin
SHELL=/bin/csh
HOSTTYPE=FreeBSD
OSTYPE=FreeBSD
MACHTYPE=i386
Signal Handlers:
SIGSEGV: [libjvm.so+0x824280], sa_mask[0]=11111111111111111111111111111110, sa_flags=SA_RESTART|SA_SIGINFO
SIGBUS: [libjvm.so+0x824280], sa_mask[0]=11111111111111111111111111111110, sa_flags=SA_RESTART|SA_SIGINFO
SIGFPE: [libjvm.so+0x6b92f0], sa_mask[0]=11111111111111111111111111111110, sa_flags=SA_RESTART|SA_SIGINFO
SIGPIPE: [libjvm.so+0x6b92f0], sa_mask[0]=11111111111111111111111111111110, sa_flags=SA_RESTART|SA_SIGINFO
SIGXFSZ: [libjvm.so+0x6b92f0], sa_mask[0]=11111111111111111111111111111110, sa_flags=SA_RESTART|SA_SIGINFO
SIGILL: [libjvm.so+0x6b92f0], sa_mask[0]=11111111111111111111111111111110, sa_flags=SA_RESTART|SA_SIGINFO
SIGUSR1: SIG_DFL, sa_mask[0]=11111111011111110111111111111111, sa_flags=none
SIGUSR2: [libjvm.so+0x6b9fe0], sa_mask[0]=00000000000000000000000000000000, sa_flags=SA_RESTART|SA_SIGINFO
SIGHUP: SIG_DFL, sa_mask[0]=00000000000000000000000000000000, sa_flags=none
SIGINT: SIG_DFL, sa_mask[0]=00000000000000000000000000000000, sa_flags=none
SIGTERM: SIG_DFL, sa_mask[0]=00000000000000000000000000000000, sa_flags=none
SIGQUIT: SIG_DFL, sa_mask[0]=00000000000000000000000000000000, sa_flags=none
--------------- S Y S T E M ---------------
OS:BSD
uname:FreeBSD 10.1-RELEASE FreeBSD 10.1-RELEASE #0 r274401: Tue Nov 11 22:51:51 UTC 2014 root#releng1.nyi.freebsd.org:/usr/obj/usr/src/sys/GENERIC i386
rlimit: STACK 65536k, CORE infinity, NPROC 5547, NOFILE 94860, AS infinity
load average:0.26 0.19 0.80
CPU:total 8 (4 cores per cpu, 1 threads per core) family 6 model 26 stepping 5, cmov, cx8, fxsr, mmx, sse, sse2, sse3, ssse3, sse4.1, sse4.2, popcnt, tsc, tscinvbit, tscinv
Memory: 4k page, physical 3372996k(2931288k free), swap 13807988388243963904k(13807988392538586972k free)
vm_info: OpenJDK Server VM (25.60-b23) for bsd-x86 JRE (1.8.0_60-b24), built on Nov 14 2015 17:53:51 by "bob" with gcc 4.2.1 Compatible FreeBSD Clang 3.4.1 (tags/RELEASE_34/dot1-final 208032)
time: Sat Nov 14 18:21:52 2015
elapsed time: 0 seconds (0d 0h 0m 0s)
All packages are up to date and compiled from source. All Java-related stuff is newly installed (along with Artifactory) and with unchanged, default configuration.
Any ideas? Thanks.

This seems to be an issue with memory allocation.
The default heap size defined in the Artifactory startup script is 2g, which is more than the maximal heap size which can be allocated by the JVM on a 32bit FreeBSD machine.
The solution in this case would be deacreasing the maximum heap size to ~1.5g.

Related

Install of elastic 7.5 on RHEL 7.8 makes memory violation sig=6 due to JNA

I am installing a brand new elasticsearch 7.5 on OS:Red Hat Enterprise Linux Server release 7.8 (Maipo)
At startup of the service, I have hard failure. here is what the service info provides
● elasticsearch.service - Elasticsearch
Loaded: loaded (/usr/lib/systemd/system/elasticsearch.service; disabled; vendor preset: disabled)
Active: failed (Result: signal) since Tue 2020-08-25 11:34:39 CEST; 7min ago
Docs: http://www.elastic.co
Process: 102777 ExecStart=/usr/share/elasticsearch/bin/elasticsearch -p ${PID_DIR}/elasticsearch.pid --quiet (code=killed, signal=ABRT)
Main PID: 102777 (code=killed, signal=ABRT)
CGroup: /system.slice/elasticsearch.service
Aug 25 11:34:34 sv-1348lvd44.esante.local systemd[1]: Starting Elasticsearch...
Aug 25 11:34:35 sv-1348lvd44.esante.local elasticsearch[102777]: OpenJDK 64-Bit Server VM warning: Option UseConcMarkSweepGC was deprecated...lease.
Aug 25 11:34:39 sv-1348lvd44.esante.local systemd[1]: elasticsearch.service: main process exited, code=killed, status=6/ABRT
Aug 25 11:34:39 sv-1348lvd44.esante.local systemd[1]: Failed to start Elasticsearch.
Aug 25 11:34:39 sv-1348lvd44.esante.local systemd[1]: Unit elasticsearch.service entered failed state.
Aug 25 11:34:39 sv-1348lvd44.esante.local systemd[1]: elasticsearch.service failed.
when using journalctl -xe
Aug 25 11:34:38 sv-1348lvd44.esante.local audispd[824]: node=sv-1348lvd44.esante.local type=ANOM_ABEND msg=audit(1598348078.836:208066): auid=429496 uid=995 gid=991 ses=4294967295 subj=system_u:system_r:unconfined_service_t:s0 pid=102777 comm="java" reason="memory violation" sig=6
Aug 25 11:34:39 sv-1348lvd44.esante.local systemd[1]: elasticsearch.service: main process exited, code=killed, status=6/ABRT
Aug 25 11:34:39 sv-1348lvd44.esante.local systemd[1]: Failed to start Elasticsearch.
when looking into the dump hs_err_pidXXXX I have.
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007f4818939b85, pid=52870, tid=52933
#
# JRE version: OpenJDK Runtime Environment (13.0.1+9) (build 13.0.1+9)
# Java VM: OpenJDK 64-Bit Server VM (13.0.1+9, mixed mode, sharing, tiered, compressed oops, concurrent mark sweep gc, linux-amd64)
# Problematic frame:
# C [jna515356041985641679.tmp+0x12b85] ffi_prep_closure_loc+0x15
[OS:Red Hat Enterprise Linux Server release 7.8 (Maipo)
uname:Linux 3.10.0-1127.10.1.el7.x86_64 #1 SMP Tue May 26 15:05:43 EDT 2020 x86_64
libc:glibc 2.17 NPTL 2.17
rlimit: STACK 8192k, CORE 0k, NPROC 4096, NOFILE 65535, AS infinity, DATA infinity, FSIZE infinity
load average:0.08 0.03 0.05
.../...
It works like a charm on CentOS without doing anything.
For RHEL, I already fixed the stuff about JNA by adding ES_TMPDIR=/var/es-temp into /etc/sysconfig/elasticsearch as
Memory seems fine. this is a brand new VM. (no application logs into /var/logs)
Seems that this version is supposed to be supported
I tested with -Xms2g -Xmx2g, -Xms1g -Xmx1g, -Xms512m -Xmx512m but same error.
I don't get what is going wrong. My Next step is to test with another version 7 of elasticsearch.
After 1 day of struggling, I found the solution at https://discuss.elastic.co/t/elasticsearch-v7-6-2-failed-to-start-killed-by-sigabrt-on-rhel-7-7-urgent/231039/11 from Ivan_A_Carrazana_C
I put here a copy of the steps to perform:
Hi
If you are applying a security compliance in your RHEL installation you must change the >path of the TMP directory that will use elasticsearch as Java.
Uncomment at /etc/elasticsearch/jvm.options
-Djava.io.tmpdir=${ES_TMPDIR}
Add in /etc /sysconfig/elasticsearch
ES_TMPDIR=/usr/share/elasticsearch/tmp
Create the /usr/share/elasticsearch/tmp directory and make sure that the owner and group >are elasticsearch and the permissions are 0755
Lastly make sure that /dev/shm doesn't have the noexec attribute with command:
mount | grep tmpfs | grep '/dev/shm'
Expected result:
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,seclabel)
If you get output like these:
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,noexec,seclabel)
Add or modify in /etc/fstab the following line:
tmpfs /dev/shm tmpfs defaults,nodev,nosuid 0 0
I had the same problem and this worked for me. Hope i can help you
Seems to be known by elastic but not documented correctly. don't undertand why the tmpfs should in noexec. Would be good to have an JNA expert feedback about it.
For some reason, adding a TMPDIR var to /etc/sysconfig/elasticsearch worked (on 7.7.1) and pointing it to the same location as -Djava.io.tmpdir.
i.e.
TMPDIR="/usr/share/elasticsearch/tmp"
(in my case I actually used /var/lib/elasticsearch/tmp with 0755 permissions on it).
I can't say why, and it doesn't change the call string used if I look at 'ps -aef' . But just having -Djava.io.tmpdir wasn't enough.
This allowed me to get it to work without removing noexec on /tmp and /dev/shm.

Container is running beyond physical memory limits

I have a MapReduce Job that process 1.4 Tb of data.
While doing it, I am getting the error as below.
The number of splits is 6444.
Before starting the job I set the following settings:
conf.set("mapreduce.map.memory.mb", "8192");
conf.set("mapreduce.reduce.memory.mb", "8192");
conf.set("mapreduce.map.java.opts.max.heap", "8192");
conf.set("mapreduce.map.java.opts", "-Xmx8192m");
conf.set("mapreduce.reduce.java.opts", "-Xmx8192m");
conf.set("mapreduce.job.heap.memory-mb.ratio", "0.8");
conf.set("mapreduce.task.timeout", "21600000");
The error:
2018-05-18 00:50:36,595 INFO [AsyncDispatcher event handler] org.apache.hadoop.mapreduce.v2.app.job.impl.TaskAttemptImpl: Diagnostics report from attempt_1524473936587_2969_m_004719_3: Container [pid=11510,containerID=container_1524473936587_2969_01_004894] is running beyond physical memory limits. Current usage: 8.1 GB of 8 GB physical memory used; 8.8 GB of 16.8 GB virtual memory used. Killing container.
Dump of the process-tree for container_1524473936587_2969_01_004894 :
|- PID PPID PGRPID SESSID CMD_NAME USER_MODE_TIME(MILLIS) SYSTEM_TIME(MILLIS) VMEM_USAGE(BYTES) RSSMEM_USAGE(PAGES) FULL_CMD_LINE
|- 11560 11510 11510 11510 (java) 14960 2833 9460879360 2133706 /usr/lib/jvm/java-7-oracle-cloudera/bin/java
-Djava.net.preferIPv4Stack=true -Dhadoop.metrics.log.level=WARN -Xmx8192m -Djava.io.tmpdir=/sdk/7/yarn/nm/usercache/administrator/appcache/application_1524473936587_2969/container_1524473936587_2969_01_004894/tmp
-Dlog4j.configuration=container-log4j.properties -Dyarn.app.container.log.dir=/var/log/hadoop-yarn/container/application_1524473936587_2969/container_1524473936587_2969_01_004894
-Dyarn.app.container.log.filesize=0 -Dhadoop.root.logger=INFO,CLA -Dhadoop.root.logfile=syslog org.apache.hadoop.mapred.YarnChild 10.106.79.75 41869 attempt_1524473936587_2969_m_004719_3 4894
|- 11510 11508 11510 11510 (bash) 0 0 11497472 679 /bin/bash -c /usr/lib/jvm/java-7-oracle-cloudera/bin/java
-Djava.net.preferIPv4Stack=true -Dhadoop.metrics.log.level=WARN -Xmx8192m -Djava.io.tmpdir=/sdk/7/yarn/nm/usercache/administrator/appcache/application_1524473936587_2969/container_1524473936587_2969_01_004894/tmp
-Dlog4j.configuration=container-log4j.properties -Dyarn.app.container.log.dir=/var/log/hadoop-yarn/container/application_1524473936587_2969/container_1524473936587_2969_01_004894
-Dyarn.app.container.log.filesize=0 -Dhadoop.root.logger=INFO,CLA -Dhadoop.root.logfile=syslog org.apache.hadoop.mapred.YarnChild 10.106.79.75 41869 attempt_1524473936587_2969_m_004719_3 4894 1>/var/log/hadoop-yarn/container/application_1524473936587_2969/container_1524473936587_2969_01_004894/stdout 2>/var/log/hadoop-yarn/container/application_1524473936587_2969/container_1524473936587_2969_01_004894/stderr
Container killed on request. Exit code is 143
Container exited with a non-zero exit code 143
Any help would be really appreciated!
The setting mapreduce.map.memory.mb will set the physical memory size of the container running the mapper (mapreduce.reduce.memory.mb will do the same for the reducer container).
Besure that you adjust the heap value as well. In newer version of YARN/MRv2 the setting mapreduce.job.heap.memory-mb.ratio can be used to have it auto-adjust. The default is .8, so 80% of whatever the container size is will be allocated as the heap. Otherwise, adjust manually using mapreduce.map.java.opts.max.heap and mapreduce.reduce.java.opts.max.heap settings.
BTW, I believe that 1 GB is the default and it is quite low. I recommend reading the below link. It provides a good understanding of YARN and MR memory setting, how they relate, and how to set some baseline settings based on the cluster node size (disk, memory, and cores).
Reference: http://community.cloudera.com/t5/Cloudera-Manager-Installation/ERROR-is-running-beyond-physical-memory-limits/td-p/55173
Try to set yarn memory allocation limits:
SET yarn.scheduler.maximum-allocation-mb=16G;
SET yarn.scheduler.minimum-allocation-mb=8G;
You may lookup other Yarn settings here:
https://www.ibm.com/support/knowledgecenter/STXKQY_BDA_SHR/bl1bda_tuneyarn.htm
Try with : set yarn.app.mapreduce.am.resource.mb=1000;
Explanation is here :
In spark, spark.driver.memoryOverhead is considered in calculating the total memory required for the driver. By default it is 0.10 of the driver-memory or minimum 384MB. In your case it will be 8GB * 0.1 = 9011MB ~= 9G
YARN allocates memory only in increments/multiples of yarn.scheduler.minimum-allocation-mb .
When yarn.scheduler.minimum-allocation-mb=4G, it can only allocate container sizes of 4G,8G,12G etc. So if something like 9G is requested it will round up to the next multiple and will allocate 12G of container size for the driver.
When yarn.scheduler.minimum-allocation-mb=1G, then container sizes of 8G, 9G, 10G are possible. The nearest rounded up size of 9G will be used in this case.
https://community.cloudera.com/t5/Support-Questions/Yarn-Container-is-running-beyond-physical-memory-limits-but/m-p/199353#M161393

RMAppMaster is running beyond physical memory limits

I am trying to troubleshoot this puzzling issue: RMAppMaster oversteps its allocated container memory and is then killed by the node manager even if heap size is much smaller than container size.
NM logs:
2017-12-01 11:18:49,863 INFO org.apache.hadoop.yarn.server.nodemanager.containermanager.monitor.ContainersMonitorImpl: Memory usage of ProcessTree 14191 for container-id container_1506599288376_62101_01_000001: 1.0 GB of 1 GB physical memory used; 3.1 GB of 2.1 GB virtual memory used
2017-12-01 11:18:49,863 WARN org.apache.hadoop.yarn.server.nodemanager.containermanager.monitor.ContainersMonitorImpl: Process tree for container: container_1506599288376_62101_01_000001 has processes older than 1 iteration running over the configured limit. Limit=1073741824, current usage = 1076969472
2017-12-01 11:18:49,863 WARN org.apache.hadoop.yarn.server.nodemanager.containermanager.monitor.ContainersMonitorImpl: Container [pid=14191,containerID=container_1506599288376_62101_01_000001] is running beyond physical memory limits. Current usage: 1.0 GB of 1 GB physical memory used; 3.1 GB of 2.1 GB virtual memory used. Killing container.
Dump of the process-tree for container_1506599288376_62101_01_000001 :
|- 14279 14191 14191 14191 (java) 4915 235 3167825920 262632 /usr/java/default//bin/java -Dlog4j.configuration=container-log4j.properties -Dyarn.app.container.log.dir=/var/log/hadoop-yarn/container/application_1506599288376_62101/container_1506599288376_62101_01_000001 -Dyarn.app.container.log.filesize=0 -Dhadoop.root.logger=INFO,CLA -Djava.net.preferIPv4Stack=true -Xmx512m org.apache.hadoop.mapreduce.v2.app.MRAppMaster
|- 14191 14189 14191 14191 (bash) 0 1 108650496 300 /bin/bash -c /usr/java/default//bin/java -Dlog4j.configuration=container-log4j.properties -Dyarn.app.container.log.dir=/var/log/hadoop-yarn/container/application_1506599288376_62101/container_1506599288376_62101_01_000001 -Dyarn.app.container.log.filesize=0 -Dhadoop.root.logger=INFO,CLA -Djava.net.preferIPv4Stack=true -Xmx512m org.apache.hadoop.mapreduce.v2.app.MRAppMaster 1>/var/log/hadoop-yarn/container/application_1506599288376_62101/container_1506599288376_62101_01_000001/stdout 2>/var/log/hadoop-yarn/container/application_1506599288376_62101/container_1506599288376_62101_01_000001/stderr
You can observe that while the heap size is set to 512MB, physical memory observed by the NM grows up to 1GB.
Application is an Oozie launcher (Hive task), thus it has only one mapper which does mostly nothing and no reducer.
What baffles me is that only this specific instance of MRAppMaster is killed and I cannot explain the 500MB overhead between max heap size and physical memory as defined by the NM:
Other MRAppMaster instances run fine even with the default config (yarn.app.mapreduce.am.resource.mb = 1024 and yarn.app.mapreduce.am.command-opts = -Xmx825955249).
MRAppMaster does not run any application specific code, why only this one is having trouble? I expect MRAppMaster memory consumption to be somewhat linear to the number of tasks / attempts and this app has only one mapper.
-Xmx has been reduced to 512MB to see if the issue still happens with ~500MB of headroom. I expect MRAppMaster to consume very little native memory, what could those extra 500MB be?
I will try to workaround the issue by increasing yarn.app.mapreduce.am.resource.mb, but had really like to understand what is going on. Any idea?
config: cdh-5.4

Qt macdeployqt - crash after using

When I run application after using macdeploy my application crashed.
I trying use SDK 4.8.5 and 5.2... but nothing to changes..
Command:
Users/ltise/Qt5.2.0/5.2.0/clang_64/bin/macdeployqt Application.app -verbose=2
Log:
Log: Deploying Qt frameworks found inside: ("Application.app/Contents/MacOS/Application")
Log: copied: "/Users/ltise/Qt5.2.0/5.2.0/clang_64/lib/QtSvg.framework/Versions/5/QtSvg"
Log: to "Application.app/Contents/Frameworks/QtSvg.framework/Versions/5/QtSvg"
Log: copy: "/Users/ltise/Qt5.2.0/5.2.0/clang_64/lib/QtSvg.framework/Resources" "Application.app/Contents/Frameworks/QtSvg.framework/Resources"
Log: copied: "/Users/ltise/Qt5.2.0/5.2.0/clang_64/lib/QtWidgets.framework/Versions/5/QtWidgets"
Log: to "Application.app/Contents/Frameworks/QtWidgets.framework/Versions/5/QtWidgets"
Log: copy: "/Users/ltise/Qt5.2.0/5.2.0/clang_64/lib/QtWidgets.framework/Resources" "Application.app/Contents/Frameworks/QtWidgets.framework/Resources"
Log: copied: "/Users/ltise/Qt5.2.0/5.2.0/clang_64/lib/QtGui.framework/Versions/5/QtGui"
Log: to "Application.app/Contents/Frameworks/QtGui.framework/Versions/5/QtGui"
Log: copy: "/Users/ltise/Qt5.2.0/5.2.0/clang_64/lib/QtGui.framework/Resources" "Application.app/Contents/Frameworks/QtGui.framework/Resources"
Log: copied: "/Users/ltise/Qt5.2.0/5.2.0/clang_64/lib/QtCore.framework/Versions/5/QtCore"
Log: to "Application.app/Contents/Frameworks/QtCore.framework/Versions/5/QtCore"
Log: copy: "/Users/ltise/Qt5.2.0/5.2.0/clang_64/lib/QtCore.framework/Resources" "Application.app/Contents/Frameworks/QtCore.framework/Resources"
Log: copied: "/Users/ltise/Qt5.2.0/5.2.0/clang_64/lib/QtOpenGL.framework/Versions/5/QtOpenGL"
Log: to "Application.app/Contents/Frameworks/QtOpenGL.framework/Versions/5/QtOpenGL"
Log: copy: "/Users/ltise/Qt5.2.0/5.2.0/clang_64/lib/QtOpenGL.framework/Resources" "Application.app/Contents/Frameworks/QtOpenGL.framework/Resources"
Log: copied: "/Users/ltise/Qt5.2.0/5.2.0/clang_64/lib/QtXml.framework/Versions/5/QtXml"
Log: to "Application.app/Contents/Frameworks/QtXml.framework/Versions/5/QtXml"
Log: copy: "/Users/ltise/Qt5.2.0/5.2.0/clang_64/lib/QtXml.framework/Resources" "Application.app/Contents/Frameworks/QtXml.framework/Resources"
Log:
Log: Deploying plugins from "/Users/ltise/Qt5.2.0/5.2.0/clang_64/plugins"
Log: copied: "/Users/ltise/Qt5.2.0/5.2.0/clang_64/plugins/platforms/libqcocoa.dylib"
Log: to "Application.app/Contents/PlugIns/platforms/libqcocoa.dylib"
Log:
Log: Deploying Qt frameworks found inside: ("Application.app/Contents/PlugIns/platforms/libqcocoa.dylib")
Log: copied: "/Users/ltise/Qt5.2.0/5.2.0/clang_64/lib/QtPrintSupport.framework/Versions/5/QtPrintSupport"
Log: to "Application.app/Contents/Frameworks/QtPrintSupport.framework/Versions/5/QtPrintSupport"
Log: copy: "/Users/ltise/Qt5.2.0/5.2.0/clang_64/lib/QtPrintSupport.framework/Resources" "Application.app/Contents/Frameworks/QtPrintSupport.framework/Resources"
Log: copied: "/Users/ltise/Qt5.2.0/5.2.0/clang_64/plugins/printsupport/libcocoaprintersupport.dylib"
Log: to "Application.app/Contents/PlugIns/printsupport/libcocoaprintersupport.dylib"
Log:
Log: Deploying Qt frameworks found inside: ("Application.app/Contents/PlugIns/printsupport/libcocoaprintersupport.dylib")
Log: copied: "/Users/ltise/Qt5.2.0/5.2.0/clang_64/plugins/accessible/libqtaccessiblewidgets.dylib"
Log: to "Application.app/Contents/PlugIns/accessible/libqtaccessiblewidgets.dylib"
Log:
Log: Deploying Qt frameworks found inside: ("Application.app/Contents/PlugIns/accessible/libqtaccessiblewidgets.dylib")
Log: copied: "/Users/ltise/Qt5.2.0/5.2.0/clang_64/plugins/imageformats/libqgif.dylib"
Log: to "Application.app/Contents/PlugIns/imageformats/libqgif.dylib"
Log:
Log: Deploying Qt frameworks found inside: ("Application.app/Contents/PlugIns/imageformats/libqgif.dylib")
Log: copied: "/Users/ltise/Qt5.2.0/5.2.0/clang_64/plugins/imageformats/libqico.dylib"
Log: to "Application.app/Contents/PlugIns/imageformats/libqico.dylib"
Log:
Log: Deploying Qt frameworks found inside: ("Application.app/Contents/PlugIns/imageformats/libqico.dylib")
Log: copied: "/Users/ltise/Qt5.2.0/5.2.0/clang_64/plugins/imageformats/libqjpeg.dylib"
Log: to "Application.app/Contents/PlugIns/imageformats/libqjpeg.dylib"
Log:
Log: Deploying Qt frameworks found inside: ("Application.app/Contents/PlugIns/imageformats/libqjpeg.dylib")
Log: copied: "/Users/ltise/Qt5.2.0/5.2.0/clang_64/plugins/imageformats/libqmng.dylib"
Log: to "Application.app/Contents/PlugIns/imageformats/libqmng.dylib"
Log:
Log: Deploying Qt frameworks found inside: ("Application.app/Contents/PlugIns/imageformats/libqmng.dylib")
Log: copied: "/Users/ltise/Qt5.2.0/5.2.0/clang_64/plugins/imageformats/libqsvg.dylib"
Log: to "Application.app/Contents/PlugIns/imageformats/libqsvg.dylib"
Log:
Log: Deploying Qt frameworks found inside: ("Application.app/Contents/PlugIns/imageformats/libqsvg.dylib")
Log: copied: "/Users/ltise/Qt5.2.0/5.2.0/clang_64/plugins/imageformats/libqsvg_debug.dylib"
Log: to "Application.app/Contents/PlugIns/imageformats/libqsvg_debug.dylib"
Log:
Log: Deploying Qt frameworks found inside: ("Application.app/Contents/PlugIns/imageformats/libqsvg_debug.dylib")
Log: copied: "/Users/ltise/Qt5.2.0/5.2.0/clang_64/plugins/imageformats/libqtga.dylib"
Log: to "Application.app/Contents/PlugIns/imageformats/libqtga.dylib"
Log:
Log: Deploying Qt frameworks found inside: ("Application.app/Contents/PlugIns/imageformats/libqtga.dylib")
Log: copied: "/Users/ltise/Qt5.2.0/5.2.0/clang_64/plugins/imageformats/libqtiff.dylib"
Log: to "Application.app/Contents/PlugIns/imageformats/libqtiff.dylib"
Log:
Log: Deploying Qt frameworks found inside: ("Application.app/Contents/PlugIns/imageformats/libqtiff.dylib")
Log: copied: "/Users/ltise/Qt5.2.0/5.2.0/clang_64/plugins/imageformats/libqwbmp.dylib"
Log: to "Application.app/Contents/PlugIns/imageformats/libqwbmp.dylib"
Log:
Log: Deploying Qt frameworks found inside: ("Application.app/Contents/PlugIns/imageformats/libqwbmp.dylib")
Log: Created configuration file: "Application.app/Contents/Resources/qt.conf"
Log: This file sets the plugin search path to "Application.app/Contents/PlugIns"
Application output to console:
Tests:~ ltise$ /Developer/Projects/Tests/build-Application-Clone_of_Desktop_Qt_5_2_0_clang_64bit2-Release/qt_debug/Application.app/Contents/MacOS/Application ; exit;
("/Users/ltise/Qt5.2.0/5.2.0/clang_64/plugins")
QObject::moveToThread: Current thread (0x1039057e0) is not the object's thread (0x1039079f0).
Cannot move to target thread (0x1039057e0)
On Mac OS X, you might be loading two sets of Qt binaries into the same process. Check that all plugins are compiled against the right Qt binaries. Export DYLD_PRINT_LIBRARIES=1 and check that only one set of binaries are being loaded.
QObject::moveToThread: Current thread (0x1039057e0) is not the object's thread (0x1039079f0).
Cannot move to target thread (0x1039057e0)
On Mac OS X, you might be loading two sets of Qt binaries into the same process. Check that all plugins are compiled against the right Qt binaries. Export DYLD_PRINT_LIBRARIES=1 and check that only one set of binaries are being loaded.
QObject::moveToThread: Current thread (0x1039057e0) is not the object's thread (0x1039079f0).
Cannot move to target thread (0x1039057e0)
On Mac OS X, you might be loading two sets of Qt binaries into the same process. Check that all plugins are compiled against the right Qt binaries. Export DYLD_PRINT_LIBRARIES=1 and check that only one set of binaries are being loaded.
QObject::moveToThread: Current thread (0x1039057e0) is not the object's thread (0x1039079f0).
Cannot move to target thread (0x1039057e0)
On Mac OS X, you might be loading two sets of Qt binaries into the same process. Check that all plugins are compiled against the right Qt binaries. Export DYLD_PRINT_LIBRARIES=1 and check that only one set of binaries are being loaded.
objc[47743]: Class NotificationReceiver is implemented in both /Developer/Projects/Tests/build-Application-Clone_of_Desktop_Qt_5_2_0_clang_64bit2-Release/qt_debug/Application.app/Contents/Frameworks/QtWidgets.framework/Versions/5/QtWidgets and /Users/ltise/Qt5.2.0/5.2.0/clang_64/lib/QtWidgets.framework/Versions/5/QtWidgets. One of the two will be used. Which one is undefined.
QObject::moveToThread: Current thread (0x1039057e0) is not the object's thread (0x1039079f0).
Cannot move to target thread (0x1039057e0)
On Mac OS X, you might be loading two sets of Qt binaries into the same process. Check that all plugins are compiled against the right Qt binaries. Export DYLD_PRINT_LIBRARIES=1 and check that only one set of binaries are being loaded.
QObject::moveToThread: Current thread (0x1039057e0) is not the object's thread (0x1039079f0).
Cannot move to target thread (0x1039057e0)
On Mac OS X, you might be loading two sets of Qt binaries into the same process. Check that all plugins are compiled against the right Qt binaries. Export DYLD_PRINT_LIBRARIES=1 and check that only one set of binaries are being loaded.
QObject::moveToThread: Current thread (0x1039057e0) is not the object's thread (0x1039079f0).
Cannot move to target thread (0x1039057e0)
On Mac OS X, you might be loading two sets of Qt binaries into the same process. Check that all plugins are compiled against the right Qt binaries. Export DYLD_PRINT_LIBRARIES=1 and check that only one set of binaries are being loaded.
QObject::moveToThread: Current thread (0x1039057e0) is not the object's thread (0x1039079f0).
Cannot move to target thread (0x1039057e0)
On Mac OS X, you might be loading two sets of Qt binaries into the same process. Check that all plugins are compiled against the right Qt binaries. Export DYLD_PRINT_LIBRARIES=1 and check that only one set of binaries are being loaded.
Support formats: ("bmp", "pbm", "pgm", "png", "ppm", "xbm", "xpm")
QObject::moveToThread: Current thread (0x1039057e0) is not the object's thread (0x1039079f0).
Cannot move to target thread (0x1039057e0)
On Mac OS X, you might be loading two sets of Qt binaries into the same process. Check that all plugins are compiled against the right Qt binaries. Export DYLD_PRINT_LIBRARIES=1 and check that only one set of binaries are being loaded.
This application failed to start because it could not find or load the Qt platform plugin "cocoa".
Available platform plugins are: cocoa, minimal, offscreen.
Reinstalling the application may fix this problem.
Abort trap: 6
logout
[Process completed]
Check otool:
otool -L Application.app/contents/macos/application
Log:
Application.app/contents/macos/Application:
/System/Library/Frameworks/GLUT.framework/Versions/A/GLUT (compatibility version 1.0.0, current version 1.0.0)
#executable_path/../Frameworks/QtSvg.framework/Versions/5/QtSvg (compatibility version 5.2.0, current version 5.2.0)
#executable_path/../Frameworks/QtWidgets.framework/Versions/5/QtWidgets (compatibility version 5.2.0, current version 5.2.0)
#executable_path/../Frameworks/QtGui.framework/Versions/5/QtGui (compatibility version 5.2.0, current version 5.2.0)
#executable_path/../Frameworks/QtCore.framework/Versions/5/QtCore (compatibility version 5.2.0, current version 5.2.0)
#executable_path/../Frameworks/QtOpenGL.framework/Versions/5/QtOpenGL (compatibility version 5.2.0, current version 5.2.0)
#executable_path/../Frameworks/QtXml.framework/Versions/5/QtXml (compatibility version 5.2.0, current version 5.2.0)
/System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL (compatibility version 1.0.0, current version 1.0.0)
/System/Library/Frameworks/AGL.framework/Versions/A/AGL (compatibility version 1.0.0, current version 1.0.0)
/usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 60.0.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1197.1.1)
Crash Report on running:
Process: Application [45439]
Path: /Developer/Projects/Vectools/build-Application-Clone_of_Desktop_Qt_5_2_0_clang_64bit2-Release/qt_debug/Application.app/Contents/MacOS/Application
Identifier: #BUNDLEIDENTIFIER#
Version: ???
Code Type: X86-64 (Native)
Parent Process: launchd [169]
Responsible: Application [45439]
User ID: 503
Date/Time: 2014-02-02 21:38:19.006 +0400
OS Version: Mac OS X 10.9.1 (13B42)
Report Version: 11
Anonymous UUID: 7B93716C-BCAF-BAA9-71E1-51752259B530
Sleep/Wake UUID: CB2DC327-2013-416E-B21F-0655A3570A07
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Application Specific Information:
abort() called
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x00007fff89f47866 __pthread_kill + 10
1 libsystem_pthread.dylib 0x00007fff8c28635c pthread_kill + 92
2 libsystem_c.dylib 0x00007fff91598bba abort + 125
3 QtCore 0x0000000100ed4b69 0x100ebb000 + 105321
4 QtCore 0x0000000100ed51a1 QMessageLogger::fatal(char const*, ...) const + 161
5 QtGui 0x0000000100a9a5cd QGuiApplicationPrivate::createPlatformIntegration() + 4333
6 QtGui 0x0000000100a9a5eb QGuiApplicationPrivate::createEventDispatcher() + 27
7 QtCore 0x00000001010cc778 QCoreApplication::init() + 104
8 QtCore 0x00000001010cc6e7 QCoreApplication::QCoreApplication(QCoreApplicationPrivate&) + 39
9 QtGui 0x0000000100a9850e QGuiApplication::QGuiApplication(QGuiApplicationPrivate&) + 14
10 QtWidgets 0x00000001004c28be QApplication::QApplication(int&, char**, int) + 206
11 #BUNDLEIDENTIFIER# 0x000000010012b85a main + 618
12 #BUNDLEIDENTIFIER# 0x0000000100004524 start + 52
Thread 1:
0 libsystem_kernel.dylib 0x00007fff89f47e6a __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff8c286f08 _pthread_wqthread + 330
2 libsystem_pthread.dylib 0x00007fff8c289fb9 start_wqthread + 13
Thread 2:: Dispatch queue: com.apple.libdispatch-manager
0 libsystem_kernel.dylib 0x00007fff89f48662 kevent64 + 10
1 libdispatch.dylib 0x00007fff92c0243d _dispatch_mgr_invoke + 239
2 libdispatch.dylib 0x00007fff92c02152 _dispatch_mgr_thread + 52
Thread 3:
0 libsystem_kernel.dylib 0x00007fff89f47e6a __workq_kernreturn + 10
1 libsystem_pthread.dylib 0x00007fff8c286f08 _pthread_wqthread + 330
2 libsystem_pthread.dylib 0x00007fff8c289fb9 start_wqthread + 13
Thread 0 crashed with X86 Thread State (64-bit):
rax: 0x0000000000000000 rbx: 0x00007fff7a579310 rcx: 0x00007fff5fbff638 rdx: 0x0000000000000000
rdi: 0x0000000000000707 rsi: 0x0000000000000006 rbp: 0x00007fff5fbff660 rsp: 0x00007fff5fbff638
r8: 0x00000001030020a0 r9: 0x0000000000000000 r10: 0x0000000008000000 r11: 0x0000000000000206
r12: 0x00007fff5fbff928 r13: 0x00007fff5fbffc20 r14: 0x0000000000000006 r15: 0x00007fff5fbff8f8
rip: 0x00007fff89f47866 rfl: 0x0000000000000206 cr2: 0x0000000100d6ece5
Logical CPU: 0
Error Code: 0x02000148
Trap Number: 133
Binary Images:
0x100000000 - 0x1002c7fff +#BUNDLEIDENTIFIER# (???) <EE932156-8537-39B5-9537-50FD73AAEB62> /Developer/Projects/Vectools/build-Application-Clone_of_Desktop_Qt_5_2_0_clang_64bit2-Release/qt_debug/Application.app/Contents/MacOS/Application
0x10039a000 - 0x1003daff7 com.apple.glut (3.6.0 - GLUT-3.6.0) <87683C90-4303-3561-9CC8-5772FDEC16F0> /System/Library/Frameworks/GLUT.framework/Versions/A/GLUT
0x10044e000 - 0x100485ff7 +QtSvg (5.2) <03531661-9BA9-3B37-B1D5-EE422B1EB00B> /Developer/Projects/Vectools/build-Application-Clone_of_Desktop_Qt_5_2_0_clang_64bit2-Release/qt_debug/Application.app/Contents/Frameworks/QtSvg.framework/Versions/5/QtSvg
0x10049a000 - 0x100951ff7 +QtWidgets (5.2) <EF8840B8-A258-3110-8B39-EDBE4E708D87> /Developer/Projects/Vectools/build-Application-Clone_of_Desktop_Qt_5_2_0_clang_64bit2-Release/qt_debug/Application.app/Contents/Frameworks/QtWidgets.framework/Versions/5/QtWidgets
0x100a77000 - 0x100df6ff7 +QtGui (5.2) <1D90F282-6151-3035-8878-C6AFB7E54E1D> /Developer/Projects/Vectools/build-Application-Clone_of_Desktop_Qt_5_2_0_clang_64bit2-Release/qt_debug/Application.app/Contents/Frameworks/QtGui.framework/Versions/5/QtGui
0x100ebb000 - 0x1013b3ff7 +QtCore (5.2) <823F3C93-3ADF-3CD3-992D-06097B4F44E5>
....................
/Developer/Projects/Vectools/build-Application-Clone_of_Desktop_Qt_5_2_0_clang_64bit2-Release/qt_debug/Application.app/Contents/Frameworks/QtCore.framework/Versions/5/QtCore
0x101437000 - 0x10147efff +QtOpenGL (5.2) <5CCDC659-2305-35DA-95F6-997237B57E28> /Developer/Projects/Vectools/build-Application-Clone_of_Desktop_Qt_5_2_0_clang_64bit2-nwind.dylib
....................
0x7fff9782a000 - 0x7fff97afefc7 com.apple.vImage (7.0 - 7.0) <D241DBFA-AC49-31E2-893D-EAAC31890C90> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/vImage
0x7fff97b6c000 - 0x7fff97b95fff com.apple.DictionaryServices (1.2 - 208) <A539A058-BA57-35EE-AA08-D0B0E835127D> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/DictionaryServices.framework/Versions/A/DictionaryServices
0x7fff97b96000 - 0x7fff97bf9ff7 com.apple.SystemConfiguration (1.13 - 1.13) <F05F4149-981B-380B-8F50-51CE804BBB89> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfiguration
External Modification Summary:
Calls made by other processes targeting this process:
task_for_pid: 1
thread_create: 0
thread_set_state: 0
Calls made by this process:
task_for_pid: 0
thread_create: 0
thread_set_state: 0
Calls made by all processes on this machine:
task_for_pid: 22215290
thread_create: 2
thread_set_state: 13573
VM Region Summary:
ReadOnly portion of Libraries: Total=211.9M resident=211.8M(100%) swapped_out_or_unallocated=92K(0%)
Writable regions: Total=51.0M written=1344K(3%) resident=1804K(3%) swapped_out=0K(0%) unallocated=49.2M(97%)
REGION TYPE VIRTUAL
=========== =======
Kernel Alloc Once 4K
MALLOC 40.4M
MALLOC (admin) 32K
STACK GUARD 56.0M
Stack 9304K
VM_ALLOCATE 328K
__DATA 22.0M
__IMAGE 528K
__LINKEDIT 72.6M
__TEXT 139.3M
__UNICODE 544K
mapped file 22.5M
shared memory 4K
=========== =======
TOTAL 363.2M
Model: MacBookPro9,2, BootROM MBP91.00D3.B08, 2 processors, Intel Core i7, 2.9 GHz, 8 GB, SMC 2.2f44
Graphics: Intel HD Graphics 4000, Intel HD Graphics 4000, Built-In, 1024 MB
Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54333531533643465238432D50422020
Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54333531533643465238432D50422020
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xF5), Broadcom BCM43xx 1.0 (5.106.98.100.22)
Bluetooth: Version 4.2.0f6 12982, 3 services, 15 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en1
Serial ATA Device: TOSHIBA MK7559GSXF, 750,16 GB
Serial ATA Device: MATSHITADVD-R UJ-8A8, 448,6 MB
USB Device: Hub
USB Device: FaceTime HD Camera (Built-in)
USB Device: Hub
USB Device: Hub
USB Device: Apple Internal Keyboard / Trackpad
USB Device: IR Receiver
USB Device: BRCM20702 Hub
USB Device: Bluetooth USB Host Controller
Thunderbolt Bus: MacBook Pro, Apple Inc., 25.1
If you have both Qt versions installed at the same time, it may give you some problems. I think I've had to give up on having both installed at the same time, because of some of the trouble it would give me during deployment.
And then it you have homebrew installed and it has a version of Qt, it can also get in the way on your Path, when the mac deploy tool is running.
Hope that helps.

when and how to use windbg kernel debugging

I found Windbg is very useful during development and debugging.
but mostly i use windbg in use mode debugging.
What kernel debugging can do in windbg?
or When should I use windbg's kernel debugging?
Is there a toturial about kernel debugging in windbg?
Thanks in advance.
you usually use kernel debugging when you need to debug low level device drivers interacting directly with the hardware.
It's more complicated to debug in kernel mode, among other things for a live kernel debug session you have to run the debugger on a different system than the one being debugged . for the majority of developers user mode is enough to do most of the work.
Advanced Windows Debugging is a very good book about debugging with wndbg (includes discussions about kernel debugging).
the dump analysis site has many tutorials including kernel debugging scenarios
the main difference between user mode and kernel mode WINDBG, is you can see EVERY process in kernel mode WINDBG, and all threads. You wont necessary get to see every stack frame since they get paged out frequently by the memory manager.
some common commands I use frequently.
!process 0 0
lists every running process:
**** NT ACTIVE PROCESS DUMP ****
PROCESS 80a02a60 Cid: 0002 Peb: 00000000 ParentCid: 0000
DirBase: 00006e05 ObjectTable: 80a03788 TableSize: 150.
Image: System
PROCESS 80986f40 Cid: 0012 Peb: 7ffde000 ParentCid: 0002
DirBase: 000bd605 ObjectTable: 8098fce8 TableSize: 38.
Image: smss.exe
PROCESS 80958020 Cid: 001a Peb: 7ffde000 ParentCid: 0012
DirBase: 0008b205 ObjectTable: 809782a8 TableSize: 150.
Image: csrss.exe
PROCESS 80955040 Cid: 0020 Peb: 7ffde000 ParentCid: 0012
DirBase: 00112005 ObjectTable: 80955ce8 TableSize: 54.
Image: winlogon.exe
PROCESS 8094fce0 Cid: 0026 Peb: 7ffde000 ParentCid: 0020
DirBase: 00055005 ObjectTable: 80950cc8 TableSize: 222.
Image: services.exe
PROCESS 8094c020 Cid: 0029 Peb: 7ffde000 ParentCid: 0020
DirBase: 000c4605 ObjectTable: 80990fe8 TableSize: 110.
Image: lsass.exe
PROCESS 809258e0 Cid: 0044 Peb: 7ffde000 ParentCid: 0026
DirBase: 001e5405 ObjectTable: 80925c68 TableSize: 70.
Image: SPOOLSS.EXE
.process {x}
Select the process you want to make active, usually followed by the !threads command to list a processes current threads.
!stacks 0x2 {foo.sys}
searches ALL threads for call stacks that contain the specified driver.
!poolused
useful when debugging low kernel memory situations and all you have is a kernel crash dump
.crash
Useful for when you are debugging live via serial cable and you want to make the target machine write a crash dump
!vm 1
Useful display of the memory managers statistics, example:
*** Virtual Memory Usage ***
Physical Memory: 16270 ( 65080 Kb)
Page File: \??\E:\pagefile.sys
Current: 98304Kb Free Space: 61044Kb
Minimum: 98304Kb Maximum: 196608Kb
Available Pages: 5543 ( 22172 Kb)
ResAvail Pages: 6759 ( 27036 Kb)
Locked IO Pages: 112 ( 448 Kb)
Free System PTEs: 45089 ( 180356 Kb)
Free NP PTEs: 5145 ( 20580 Kb)
Free Special NP: 336 ( 1344 Kb)
Modified Pages: 714 ( 2856 Kb)
NonPagedPool Usage: 877 ( 3508 Kb)
NonPagedPool Max: 6252 ( 25008 Kb)
PagedPool 0 Usage: 729 ( 2916 Kb)
PagedPool 1 Usage: 432 ( 1728 Kb)
PagedPool 2 Usage: 436 ( 1744 Kb)
PagedPool Usage: 1597 ( 6388 Kb)
PagedPool Maximum: 13312 ( 53248 Kb)
Shared Commit: 1097 ( 4388 Kb)
Special Pool: 229 ( 916 Kb)
Shared Process: 1956 ( 7824 Kb)
PagedPool Commit: 1597 ( 6388 Kb)
Driver Commit: 828 ( 3312 Kb)
Committed pages: 21949 ( 87796 Kb)
Commit limit: 36256 ( 145024 Kb)
And don't forget the ALL MIGHTY !locks
absolutely essential for troubleshooting a deadlocked machine,
kd> !locks
**** DUMP OF ALL RESOURCE OBJECTS ****
KD: Scanning for held locks......
Resource # 0x80e97620 Shared 4 owning threads
Threads: ff688da0-01<*> ff687da0-01<*> ff686da0-01<*> ff685da0-01<*>
KD: Scanning for held locks.......................................................
Resource # 0x80e23f38 Shared 1 owning threads
Threads: 80ed0023-01<*> *** Actual Thread 80ed0020
KD: Scanning for held locks.
Resource # 0x80d8b0b0 Shared 1 owning threads
Threads: 80ed0023-01<*> *** Actual Thread 80ed0020
2263 total locks, 3 locks currently held
using this command you can track down threads that are stuck waiting for another thread to release an ERESOURCE
Probably, you'll only want to debug in kernel mode when your code is running in kernel mode, ie when you're writing a drivers or something else that runs in the kernel. Or possibly if you're trying to learn more about Windows itself at a very low level by exploring around in the kernel and poking and prodding at things.
When looking for tutorials and other reference material, you might look for "kd" references as well as they are likely to be very similar. (kd is a command line kernel debugging tool.)

Resources