What happened to backward_ros?

General
,
1

The backward_ros package is great. It gives you a stack trace when your ros2 application crashes.
We’re on rolling distro and since about a couple of months ago, backward_ros has stopped working. Now all you see is a stack trace with hex addresses.

Is this the experience for others on rolling?

1 Like
2

You should probably open an issue on the repo and provide enough info so that others can reproduce your issue.

2 Likes
3

Seconding what @christophebedard said. A friendly ping on the repository is probably enough. I bet their team has been busy with ROSCon Es, IROS, and ROSCon and probably overlooked something.

For those who are curious like I was, this is the package and it looks really great.

1 Like
4

I guess I was curious if others were experiencing the same behavior but sure I’ll open an issue on the repo

1 Like
5

Hello @thejeeb!

Please open up an issue and a minimal example to reproduce the issue.

Thank you!

2 Likes
6

Hi @saikishor
In the ‘backwards_ros’ github link attached by @Katherine_Scott , I was able to get the latest foxy-devel branch to build successfully for a ROS2 Jazzy built from source in Ubuntu 22.04. While probably just semantics than an actual issue, is there any plan to change the default branch’s name to say “rolling” or publishing a dedicated “jazzy” branch?

7

Hello. @azmyin12!

Currently, there is no plan to change branch from foxy-devel, unless there is a breaking change coming into a specific distro. I hope this answers your question.

Thank you!

8

Hi, thanks for the reply.

9

FYI, I wrote a test application and reproduced the issue with backward_ros i.e. not giving a source stack trace. I then noticed there were some changes to backward_ros in the last day. So I built backward_ros locally and now it works for me and gives me a proper trace.

So version 1.0.5 which is what is currently released doesn’t work. Just to be clear, this was for ros2 rolling on Ubuntu 24.04. But the latest 1.0.6 version does work for me. I verified that it was this commit that fixed the issue.

10

@thejeeb Yes, it is fixed today and it is already released into all ROS 2 Distros. You just have to wait for the sync or compile it locally till then. In future, I would recommend keeping this kind of issues to GitHub issues.

Thank you.

2 Likes