I am using gdb to examine a core file but the output contains only the method addresses in hex.
Is there anyway to translate these addresses to a human-readable form? :confused: (0 Replies)
I am trying to print a stack trace programatically using backtrace and backtrace_symbols.
The problem is that the stack being printed in a mangled format. Is there a way to get the output in more of a human readable form?
I am using Red Hat and the program is written in c++. (2 Replies)
Hi all,
One of our programs written in Java, produced this logfile. This job runs 48 threads and only one thread failed with this error. The code is a blackbox(external product), so cant look at the source code. From what I can infer from the log, the job was trying to write the log messages into... (9 Replies)
I'm on solaris 8. I need to check the stack trace inside my C program. I don't have printstack or walkstack. I tested getcontext and it works. But how do I get the symbols from "stack_t" ? Help please. Many thanks! (4 Replies)
Hello ,
I use Solaris 5.10 . I have huge core file , 48 GB , resulted from an application that was running and got crashed with SIGSEGV.
On my system only mdb works. Please help me to retrieve the stack trace from this core file.
I am novice to mdb and its nuaunces. Please help me with... (2 Replies)
Hi All,
I am trying to debug my core file using kdb.
When I try to get the stack trace I am facing this error.
core mapped from @ 700000000000000 to @ 70000000306fc04
Preserving 1680415 bytes of symbol table
Dump does not start with valid magic number
WARNING: Possibly truncated or... (2 Replies)
Hi All
Thought it would be kind of fun to implement a stack trace for a shell script that calls functions within a sub shell. This is for bash under Linux and probably not portable -
#! /bin/bash
error_exit()
{
echo "======================="
echo $1
echo... (4 Replies)
I have a C program which is running as daemon and has some threads.
The program is running on dual core cpu and it may happen that different threads may run on different cpu core.
The problem is sometimes it crashes with some heap memory corruption probably between threads.
GDB command(t a a... (2 Replies)
Hi everyone,
Our Red Hat server hung yesterday, and I managed to log into the console and see the following message:
RIP: 0010: mwait_idle_with_hints+0x66/
0x67
RSP: 0018:ffffffff80457f40 EFLAGS: 00000046
RAX: 0000000000000010 RBX: ffff810c20075910 RCX: 0000000000000001
RDX:... (6 Replies)
I want the developers to get a mail with Java stack traces on a daily bases. When something is flaged as known issue and will get a fix but mean while this does not need to get sent each dayl. This is what I got so far. It's a bash script that runs some AWK in it.
To get the files that needs to... (6 Replies)
Discussion started by: chipmunken
6 Replies
LEARN ABOUT OSX
git-check-attr
GIT-CHECK-ATTR(1) Git Manual GIT-CHECK-ATTR(1)NAME
git-check-attr - Display gitattributes information
SYNOPSIS
git check-attr [-a | --all | attr...] [--] pathname...
git check-attr --stdin [-z] [-a | --all | attr...]
DESCRIPTION
For every pathname, this command will list if each attribute is unspecified, set, or unset as a gitattribute on that pathname.
OPTIONS -a, --all
List all attributes that are associated with the specified paths. If this option is used, then unspecified attributes will not be
included in the output.
--cached
Consider .gitattributes in the index only, ignoring the working tree.
--stdin
Read pathnames from the standard input, one per line, instead of from the command-line.
-z
The output format is modified to be machine-parseable. If --stdin is also given, input paths are separated with a NUL character instead
of a linefeed character.
--
Interpret all preceding arguments as attributes and all following arguments as path names.
If none of --stdin, --all, or -- is used, the first argument will be treated as an attribute and the rest of the arguments as pathnames.
OUTPUT
The output is of the form: <path> COLON SP <attribute> COLON SP <info> LF
unless -z is in effect, in which case NUL is used as delimiter: <path> NUL <attribute> NUL <info> NUL
<path> is the path of a file being queried, <attribute> is an attribute being queried and <info> can be either:
unspecified
when the attribute is not defined for the path.
unset
when the attribute is defined as false.
set
when the attribute is defined as true.
<value>
when a value has been assigned to the attribute.
Buffering happens as documented under the GIT_FLUSH option in git(1). The caller is responsible for avoiding deadlocks caused by
overfilling an input buffer or reading from an empty output buffer.
EXAMPLES
In the examples, the following .gitattributes file is used:
*.java diff=java -crlf myAttr
NoMyAttr.java !myAttr
README caveat=unspecified
o Listing a single attribute:
$ git check-attr diff org/example/MyClass.java
org/example/MyClass.java: diff: java
o Listing multiple attributes for a file:
$ git check-attr crlf diff myAttr -- org/example/MyClass.java
org/example/MyClass.java: crlf: unset
org/example/MyClass.java: diff: java
org/example/MyClass.java: myAttr: set
o Listing all attributes for a file:
$ git check-attr --all -- org/example/MyClass.java
org/example/MyClass.java: diff: java
org/example/MyClass.java: myAttr: set
o Listing an attribute for multiple files:
$ git check-attr myAttr -- org/example/MyClass.java org/example/NoMyAttr.java
org/example/MyClass.java: myAttr: set
org/example/NoMyAttr.java: myAttr: unspecified
o Not all values are equally unambiguous:
$ git check-attr caveat README
README: caveat: unspecified
SEE ALSO gitattributes(5).
GIT
Part of the git(1) suite
Git 2.17.1 10/05/2018 GIT-CHECK-ATTR(1)