8000 coredumpctl: core backtrace is useless · Issue #1656 · abrt/abrt · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
8000

coredumpctl: core backtrace is useless #1656

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
msrb opened this issue Feb 17, 2024 · 0 comments
Open

coredumpctl: core backtrace is useless #1656

msrb opened this issue Feb 17, 2024 · 0 comments

Comments

@msrb
Copy link
Member
msrb commented Feb 17, 2024

This happens on aarch64:

           PID: 3219 (will_segfault)
           UID: 1000 (michal)
           GID: 1000 (michal)
        Signal: 11 (SEGV)
     Timestamp: Sat 2024-02-17 21:53:16 CET (2min 21s ago)
  Command Line: will_segfault
    Executable: /usr/bin/will_segfault
 Control Group: /user.slice/user-1000.slice/user@1000.service/app.slice/app-org.gnome.Terminal.slice/vte-spawn-5bdca802-2875-4464-9245-0266a414b601.scope
          Unit: user@1000.service
     User Unit: vte-spawn-5bdca802-2875-4464-9245-0266a414b601.scope
         Slice: user-1000.slice
     Owner UID: 1000 (michal)
       Boot ID: 30727bd445334fc89dabad3a98c2e4d6
    Machine ID: 2a8ad4eeb2a74e22832e27803c6b1e09
      Hostname: fedora
       Storage: /var/lib/systemd/coredump/core.will_segfault.1000.30727bd445334fc89dabad3a98c2e4d6.3219.1708203196000000.zst (present)
  Size on Disk: 16.5K
       Package: will-crash/0.13.5-5.fc40
      build-id: 5aa9119f2f1080ede76b0b17fb0103a9b1393990
       Message: Process 3219 (will_segfault) of user 1000 dumped core.
                
                Module libwillcrash.so from rpm will-crash-0.13.5-5.fc40.aarch64
                Module will_segfault from rpm will-crash-0.13.5-5.fc40.aarch64
                Stack trace of thread 3219:
                #0  0x0000aaaaca9d02dc crash.constprop.0 (will_segfault + 0x102dc)
                #1  0x0070aaaaca9d0370 n/a (n/a + 0x0)
                #2  0x0070aaaaca9d0370 n/a (n/a + 0x0)
                #3  0x004faaaaca9d03bc n/a (n/a + 0x0)
                #4  0x005daaaaca9d03fc n/a (n/a + 0x0)
                #5  0x007effff8df1019c n/a (n/a + 0x0)
                #6  0x0075aaaaca9d029c n/a (n/a + 0x0)
                #7  0x0007aaaaca9d00ec n/a (n/a + 0x0)
                #8  0x0072ffff8dd409dc n/a (n/a + 0x0)
                #9  0x0013ffff8dd40abc n/a (n/a + 0x0)
                #10 0x0076aaaaca9d0170 n/a (n/a + 0x0)
                ELF object binary architecture: AARCH64

For some reason, the core backtrace from coredumpctl is completely useless. abrt relies on this core backtrace for ureports. coredumpctl gdb then produces a good backtrace.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@msrb
0