Can GNOME Abrt's "not enough information" error be bypassed?

The reason is that I do have enough information, in the form of a coredump which does produce a non-scrambed bt:

  1. RokeJulianLockhart@Beedell:~$ flatpak run --command=sh --devel com.github.Murmele.Gittyup
    [📦 com.github.Murmele.Gittyup ~]$ perf record --call-graph dwarf gittyup
    Failed to read max cpus, using default of 4096
    libperf: Miscounted nr_mmaps 0 vs 1
    WARNING: No sample_id_all support, falling back to unordered processing
    perf: Segmentation fault
    Obtained 15 stack frames.
    perf(dump_stack+0x37) [0x5614639dbcc7]
    perf(sighandler_dump_stack+0x2f) [0x5614639dbd6f]
    /usr/lib/x86_64-linux-gnu/libc.so.6(+0x3ee80) [0x7f1946251e80]
    perf(perf_cpu_map__max+0x4) [0x5614638bec14]
    perf(+0x271f74) [0x561463a34f74]
    perf(perf_event__synthesize_cpu_map+0x56) [0x561463a37dd6]
    perf(+0x8a28b) [0x56146384d28b]
    perf(+0x8dd7f) [0x561463850d7f]
    perf(cmd_record+0xe37) [0x561463854017]
    perf(+0xf8cf2) [0x5614638bbcf2]
    perf(+0xf8ffb) [0x5614638bbffb]
    perf(main+0x2e7) [0x56146383adb7]
    /usr/lib/x86_64-linux-gnu/libc.so.6(+0x2808a) [0x7f194623b08a]
    /usr/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0x8b) [0x7f194623b14b]
    perf(_start+0x25) [0x56146383b405]
    Segmentation fault (core dumped)
    
    1. [📦 com.github.Murmele.Gittyup ~]$ gdb --args 'perf' 'record' '--call-graph' 'dwarf' 'gittyup'
      GNU gdb (GDB) 16.2
      Copyright (C) 2024 Free Software Foundation, Inc.
      License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
      This is free software: you are free to change and redistribute it.
      There is NO WARRANTY, to the extent permitted by law.
      Type "show copying" and "show warranty" for details.
      This GDB was configured as "x86_64-unknown-linux-gnu".
      Type "show configuration" for configuration details.
      For bug reporting instructions, please see:
      <https://www.gnu.org/software/gdb/bugs/>.
      Find the GDB manual and other documentation resources online at:
          <http://www.gnu.org/software/gdb/documentation/>.
      
      For help, type "help".
      Type "apropos word" to search for commands related to "word"...
      Reading symbols from perf...
      Reading symbols from /usr/lib/debug/usr/bin/perf.debug...
      (gdb) run
      Starting program: /usr/bin/perf record --call-graph dwarf gittyup
      
      This GDB supports auto-downloading debuginfo from the following URLs:
        <https://debuginfod.fedoraproject.org/>
      Enable debuginfod for this session? (y or [n]) y
      Debuginfod has been enabled.
      To make this setting permanent, add 'set debuginfod enabled on' to .gdbinit.
      [Thread debugging using libthread_db enabled]
      Using host libthread_db library "/usr/lib/x86_64-linux-gnu/libthread_db.so.1".
      Failed to read max cpus, using default of 4096
      [Detaching after fork from child process 18]
      libperf: Miscounted nr_mmaps 0 vs 1
      WARNING: No sample_id_all support, falling back to unordered processing
      
    2. Program received signal SIGSEGV, Segmentation fault.
      perf_cpu_map__max (map=0x0) at cpumap.c:362
      362             return __perf_cpu_map__nr(map) > 0
      (gdb) bt full
      #0  perf_cpu_map__max (map=0x0) at cpumap.c:362
              result = {cpu = -1}
      #1  0x00005555557c5f74 in cpu_map_data__alloc (syn_data=syn_data@entry=0x7fffffff7790, header_size=header_size@entry=8) at util/synthetic-events.c:1289
              size_cpus = <optimized out>
              size_mask = <optimized out>
      #2  0x00005555557c8dd6 in cpu_map_event__new (map=<optimized out>) at util/synthetic-events.c:1337
              syn_data = {map = 0x0, nr = 1, min_cpu = -1, max_cpu = 0, has_any_cpu = 1, type = 0, size = 0, data = 0x0}
              event = <optimized out>
              syn_data = <optimized out>
              event = <error reading variable event (Cannot access memory at address 0x0)>
      #3  perf_event__synthesize_cpu_map (tool=tool@entry=0x555555f10d80 <record>, map=<optimized out>, process=process@entry=0x5555555e0270 <process_synthesized_event>, machine=machine@entry=0x0) at util/synthetic-events.c:1357
              event = <optimized out>
              err = <optimized out>
      #4  0x00005555555de28b in record__synthesize (tail=tail@entry=false, rec=0x555555f10d80 <record>) at builtin-record.c:2099
              session = 0x555555f4a830
              machine = 0x555555f4aa48
              data = 0x555555f10fc8 <record+584>
              opts = 0x555555f10ec0 <record+320>
              tool = 0x555555f10d80 <record>
              err = 0
              f = 0x5555555e0270 <process_synthesized_event>
              out = <optimized out>
      #5  0x00005555555e1d7f in __cmd_record (argc=argc@entry=1, argv=argv@entry=0x7fffffffd410, rec=0x555555f10d80 <record>) at builtin-record.c:2539
              err = <optimized out>
              status = 0
              forks = true
              tool = 0x555555f10d80 <record>
              opts = 0x555555f10ec0 <record+320>
              data = 0x555555f10fc8 <record+584>
              session = 0x555555f4a830
              disabled = false
      --Type <RET> for more, q to quit, c to continue without paging--c
              draining = false
              fd = 3
              ratio = 0
              cmd = EVLIST_CTL_CMD_UNSUPPORTED
      #6  0x00005555555e5017 in cmd_record (argc=<optimized out>, argv=<optimized out>) at builtin-record.c:4260
              err = <optimized out>
              rec = 0x555555f10d80 <record>
              errbuf = '\000' <repeats 2280 times>...
      #7  0x000055555564ccf2 in run_builtin (p=p@entry=0x555555f1c720 <commands+288>, argc=argc@entry=4, argv=argv@entry=0x7fffffffd410) at perf.c:351
              status = <optimized out>
              st = {st_dev = 93825002648512, st_ino = 93825002652944, st_nlink = 140737488343280, st_mode = 898607616, st_uid = 4080433966, st_gid = 32, __pad0 = 0, st_rdev = 140737488344080, st_size = 140737488350882, st_blksize = -921413635353368064, 
                st_blocks = 140737488343472, st_atim = {tv_sec = 140737335991347, tv_nsec = 140737488350882}, st_mtim = {tv_sec = 2, tv_nsec = 140737488343472}, st_ctim = {tv_sec = 93825002655776, tv_nsec = 93825002655808}, __glibc_reserved = {
                  140737337308368, 140737488343344, 140737336478438}}
              sbuf = "Ж\343\366\377\177\000\000\020Q\364UUU\000\0000\321\377\377\000\000\000\000(P\364UUU\000\000\000\000\000\000\000\000\000\000\3204\377\366\377\177\000\000Ж\343\366\377\177\000\000\235\356\377\377\377\177\000\000\310N\364UUU\000\000\000\252\2175.{6\363\340\321\377\377\377\177\000\000\207_oUUU\000\000\000\000\000\b\000\000\000\000\300P\364UUU\000\000\260\321\377\377\377\177\000\0003\331\377\377\377\177\000"
              out = <optimized out>
      #8  0x000055555564cffb in handle_internal_command (argc=argc@entry=4, argv=argv@entry=0x7fffffffd410) at perf.c:404
              p = 0x555555f1c720 <commands+288>
              cmd = 0x7fffffffd933 "record"
              i = 12
      #9  0x00005555555cbdb7 in run_argv (argv=<synthetic pointer>, argcp=<synthetic pointer>) at perf.c:448
      No locals.
      #10 main (argc=<optimized out>, argv=0x7fffffffd410) at perf.c:556
              err = <optimized out>
              done_help = 0
              cmd = 0x7fffffffd933 "record"
              sbuf = "\000\000\000\000\000\000\000\000\200\322\377\377\377\177\000\000\000\322\377\377\377\177\000\000\000\000\000\000\000\000\000\000\3003\364UUU\000\000p\322\377\377\377\177\000\000\3003\364UUU\000\000\240\357\362UUU", '\000' <repeats 26 times>, "\002\000\000\000\000\000\000\000\002\000\000\000\002\000\000\000\240G\364UUU\000\000\343\006\205UUU\000\000\343\006\205UUU\000"
      

However, it’s inside the flatpak sandbox, so gnome-abrt can’t process it:

The reason I’d like to use gnome-abrt anyway is because it automatically attaches environment information. (Fedora has no setuptools equivalent except gnome-abrt):

I doubt it, after going through the GUI configurator, so I’ve filed an enhancement:

1 Like

For flatpak applications, this guide may be helpful. But yes, GNOME Abrt (and the underlying libreport) does not support it.

@genodeftest, that’s not the sole instance in which I’d want this. Sometimes, the user can get a useful stack trace with a little wrangling where abrt can’t. If there’s a big banner that abuse of this mechanism means suspension of the user’s RHBZ account, I don’t envision it being utilised to post useless bugs.

Thanks, although, hopefully, the attached trace demonstrates that I’m familiar with it.

I have never heard of or seen such a banner :-o

1 Like

@genodeftest, I meant it as a suggestion. :grin:

1 Like