Stack Tracing issue

Hello,

I'm encountering an issue with my OpenWrt setup and need some assistance. Below are the details of the problem:

Issue Description: I'm experiencing a application stack trace issue. Here is a snippet of the output:

i was finding the identifier of the process i want to check
and moved to the directory(/proc/pid) and check
cat stack
[<0>] 0xffffffff

  • **OpenWrt Version:OpenWrt 21.02.1
  • **Hardware:broadcom
    1. find the id of process
    2. move to "/proc/pid/
    3. cat stack

i wanna see normal stack tracing log. but i cant. i just enabled the feature of CONFIG_STACKTRACING. is there other stepts i should do to see normal sack tracing log?

I'm seeking guidance on how to resolve this issue or any pointers on where to investigate further. Any help or suggestions would be greatly appreciated.

Thank you!

The 21.02 series has been EOL and unsupported for over a year now. Further, the series went up to 21.02.7, so you're behind on that...

what is the output of:

ubus call system board

root@mygateway:~# ubus call system board
{
"kernel": "4.19.235",
"hostname": "mygateway",
"system": "ARMv7 Processor rev 5 (v7l)",
"board_name": "brcm,bcm963178",
"release": {
"distribution": "OpenWrt",
"version": "21.02.1",
"revision": "r16325-88151b8303",
"target": "brcmbca/bcm963178",
"description": "OpenWrt 21.02.1 r16325-88151b8303"
}
}

It appears you are using firmware that is not from the official OpenWrt project.

When using forks/offshoots/vendor-specific builds that are "based on OpenWrt", there may be many differences compared to the official versions (hosted by OpenWrt.org). Some of these customizations may fundamentally change the way that OpenWrt works. You might need help from people with specific/specialized knowledge about the firmware you are using, so it is possible that advice you get here may not be useful.

You may find that the best options are:

  1. Install an official version of OpenWrt, if your device is supported (see https://firmware-selector.openwrt.org).
  2. Ask for help from the maintainer(s) or user community of the specific firmware that you are using.
  3. Provide the source code for the firmware so that users on this forum can understand how your firmware works (OpenWrt forum users are volunteers, so somebody might look at the code if they have time and are interested in your issue).

If you believe that this specific issue is common to generic/official OpenWrt and/or the maintainers of your build have indicated as such, please feel free to clarify.

1 Like