The site is read-only. Please transition to use Robotics Stack Exchange
| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
 | 1 | initial version |
Seems I misread what you wanted.
Is it possible to run my node in gdb in the same xterm as my launch with having to manually type run to start it?
I initially thought you wanted without having to manually type run .., hence my confusion.
According to Debugging with GDB - File Options - 2.1.1 Choosing Files:
-ex command
Execute a single gdb command.
You tried gdb -ex run --args. I would assume gdb --args should do what you want (ie: start gdb with the specified executable, but not run it).
| | 2 | No.2 Revision |
Seems I misread what you wanted.
Is it possible to run my node in gdb in the same xterm as my launch with having to manually type run to start it?
I initially thought you wanted without with-out having to manually type run .., hence my confusion.
According to Debugging with GDB - File Options - 2.1.1 Choosing Files:
-ex command
Execute a single gdb command.
You tried gdb -ex run --args. I would assume gdb --args should do what you want (ie: start gdb with the specified executable, but not run it).
| | 3 | No.3 Revision |
Seems I misread what you wanted.
Is it possible to run my node in gdb in the same xterm as my launch with having to manually type run to start it?
I initially thought you wanted with-out having to manually type run .., hence my confusion.
According to Debugging with GDB - File Options - 2.1.1 Choosing Files:
-ex command
Execute a single gdb command.
You tried gdb -ex run --args. I would assume gdb --args should do what you want (ie: start gdb with the specified executable, but not run it).
Edit: btw, I've assumed you want to start your node(s) using launch files. That is obviously not required, you could just as well start the node you want to debug with gdb --args /path/to/node/binary ARGS. But that would be in a separate terminal, so may not be what you want.
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
