You want `info locals`.  Or, if you are getting a back trace, `bt full`.

You can attach `info locals` to a breakpoint with the `commands` command.

&lt;!-- language-all: lang-xml --&gt;

How is placeholder `${project.version}` resolved for managed properties from parent pom? I&#39;ve expected that it is resolved globally, so when the parent pom has version 2, `${project.version}` would also be resolved to version 2.

In parent pom I have:

	&lt;groupId&gt;my.group&lt;/groupId&gt;
	&lt;artifactId&gt;parent&lt;/artifactId&gt;
	&lt;version&gt;2&lt;/version&gt;
	&lt;packaging&gt;pom&lt;/packaging&gt;

	&lt;dependencyManagement&gt;
	    &lt;dependencies&gt;
			&lt;dependency&gt;
				&lt;groupId&gt;my.group&lt;/groupId&gt;
				&lt;artifactId&gt;dep&lt;/artifactId&gt;
				&lt;version&gt;${project.version}&lt;/version&gt;
			&lt;/dependency&gt;
		&lt;/dependencies&gt;
	&lt;/dependencyManagement&gt;		

In child I use 

	&lt;parent&gt;
		&lt;groupId&gt;my.group&lt;/groupId&gt;
		&lt;artifactId&gt;parent&lt;/artifactId&gt;
		&lt;version&gt;2&lt;/version&gt;
	&lt;/parent&gt;
	&lt;version&gt;1&lt;/version&gt;
	&lt;artifactId&gt;child&lt;/artifactId&gt;

But the artifact `my.group.dep.1.jar` is used, instead of `my.group.dep.2.jar`. So the placeholder is resolved to the version of the project **using** the managed dependency, and not those of the project **defining** the dependency.

Is that expected behaviour? I&#39;m using **maven 3.0.4.**

Maven managed dependencies - resolving ${project.version} from parent pom

http://jsfiddle.net/kn5sH/

What do I need to add in order to stick the button to the right side of the div on the same line as the header?

HTML:

    &lt;div&gt;
        &lt;h1&gt; Ok &lt;/h1&gt;
        &lt;button type=&#39;button&#39;&gt;Button&lt;/button&gt;
    &lt;/div&gt;

CSS:

    div {
        background: purple;
    }

    div h1 {
        text-align: center;
    }

    div button {
    }


More specifically:

 1. The right side of the button should be x pixels away from the right
    edge of the div.
 2. It should be on the same line as the header.
 3. Should be contained in the div (stuff like float or relative
    positioning pops it out of the div visually)

What CSS techniques can be used to do this?  Thanks.

Stick button to right side of div

In gdb, after reaching a breakpoint, I want to list all the variables in the current context, instead of giving each variable name explicitly? Is there any way to achieve this at all?

How to list all variables in the current context in gdb?

<p>In gdb, after reaching a breakpoint, I want to list all the variables in the current context, instead of giving each variable name explicitly? Is there any way to achieve this at all?</p>


Is there an equivalent command in GDB to that of WinDbg&#39;s `!process 0 7`?

I want to extract all the threads in a dump file along with their backtraces in GDB. `info threads` doesn&#39;t output the stack traces. So, is there a command that does?


How do I get the backtrace for all the threads in GDB?

I&#39;m under osx 10.8.4 and have installed gdb 7.5.1 with homebrew (motivation get a new gdb with  new features such as --with-python etc... )

Long story short when I run debug within a c++ Eclipse project I get :


    Error in final launch sequence
    Failed to execute MI command:
    -exec-run
    Error message from debugger back end:
    Unable to find Mach task port for process-id 46234: (os/kern) failure (0x5).
     (please check gdb is codesigned - see taskgated(8))
    Unable to find Mach task port for process-id 46234: (os/kern) failure (0x5).
     (please check gdb is codesigned - see taskgated(8))

I have followed various suggestions for code signing

- https://sourceware.org/gdb/wiki/BuildingOnDarwin
- partly http://www.noktec.be/archives/1251 with various adjusts

So I did:

1. Set up the certificate
2. Sign the gdb -&gt; codesign -s gdb-cert /usr/local/bin/gdb

When I re-run debugging in Eclipse I get same error as above &quot;(please check gdb is codesigned - see taskgated(8))&quot;.

If I set back the gdb to the older gdb (in the gdb preferences of Eclipse) /usr/libexec/gdb/gdb-i386-apple-darwin the debugging runs as expected.

Any solutions / hints out there ?

Thx

Pelle

&quot;please check gdb is codesigned - see taskgated(8)&quot; - How to get gdb installed with homebrew code signed?

I&#39;m trying to attach a program with gdb but it returns:

&gt; Attaching to process 29139  
&gt;     Could not attach to process.  If your uid matches the uid of the target
&gt;     process, check the setting of /proc/sys/kernel/yama/ptrace_scope, or try
&gt;     again as the root user.  For more details, see /etc/sysctl.d/10-ptrace.conf  
&gt;     ptrace: Operation not permitted.

gdb-debugger returns &quot;Failed to attach to process, please check privileges and try again.&quot;

strace returns &quot;attach: ptrace(PTRACE_ATTACH, ...): Operation not permitted&quot;

I changed &quot;kernel.yama.ptrace_scope&quot; 1 to 0 and `/proc/sys/kernel/yama/ptrace_scope` 1 to 0 and tried `set environment LD_PRELOAD=./ptrace.so` with this:

    #include &lt;stdio.h&gt;
    int ptrace(int i, int j, int k, int l) {
        printf(&quot; ptrace(%i, %i, %i, %i), returning -1\n&quot;, i, j, k, l);
        return 0;
    }

But it still returns the same error. How can I attach it to debuggers?

How to solve &quot;ptrace operation not permitted&quot; when trying to attach GDB to a process?

I went to use GDB in OS X v10.9 (Mavericks), and it&#39;s not there. Where has it gone?

    # /usr/lib/gdb
    -bash: /usr/bin/gdb: No such file or directory
    # gdb
    -bash: gdb: command not found

I also launched Xcode 5.0.1:

&gt; Preferences &gt; Downloads

..and there&#39;s no longer command line tools available — ffs!


GDB missing in OS X v10.9 (Mavericks)

(Preface: I&#39;m pretty new to C/C++ and I don&#39;t really know how debugging in native code actually works.)

Some sources say that gdb and lldb can debug [any program compiled to machine code](http://www.lego.com/en-us/mindstorms/products/fan-made-bonus-robots/ev3meg). Others say that to debug with gdb you **must** compile in gcc [with the `-g` flag](http://tedlab.mit.edu/~dr/gdbintro.html). The documentation for gcc itself suggests this is optional, and that in fact if you use it, it can cause problems for debuggers _other than_ gdb. Clang also has a `-g` flag and the documentation basically just says &quot;Generate debug information.&quot;

So are these debuggers restricted to their own toolchains (GNU and LLVM), or are they somehow independent of the compiler used?

Content Type	Original Author	Original Content on Stackoverflow
Question	Hailiang Zhang	View Question on Stackoverflow
Solution 1 - Gdb	Tom Tromey	View Answer on Stackoverflow

How to list all variables in the current context in gdb?

Gdb Problem Overview

Gdb Solutions

Solution 1 - Gdb

Stick button to right side of div

Maven managed dependencies - resolving ${project.version} from parent pom

Attributions