[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1018061: pads: segfault at 3a ip



New Backtrace: 

coredumpctl gdb -1
           PID: 1546 (pads)
           UID: 0 (root)
           GID: 0 (root)
        Signal: 11 (SEGV)
     Timestamp: Tue 2023-02-07 10:08:03 CST (3h 14min ago)
  Command Line: /usr/bin/pads -D -c /etc/pads/pads.conf
    Executable: /usr/bin/pads
 Control Group: /system.slice/pads.service
          Unit: pads.service
         Slice: system.slice
       Boot ID: 90f7db29bc44436f8b4d1a2cbfc52a5c
    Machine ID: dacda8ffae4a44148edc6518f73d4b00
      Hostname: DebianTim
       Storage:
/var/lib/systemd/coredump/core.pads.0.90f7db29bc44436f8b4d1a2cbfc52a5c.
1546.1675786083000000.zst (present)
  Size on Disk: 329.8K
       Message: Process 1546 (pads) of user 0 dumped core.
                
                Module libsystemd.so.0 from deb systemd-252.5-2.amd64
                Stack trace of thread 1546:
                #0  0x00005641638af954 print_arp_asset_screen (pads +
0x9954)
                #1  0x00005641638af6f0 print_arp_asset (pads + 0x96f0)
                #2  0x00007fa6dbe004f6 n/a (libpcap.so.0.8 + 0x84f6)
                #3  0x00007fa6dbe008ec n/a (libpcap.so.0.8 + 0x88ec)
                #4  0x00007fa6dbe07d1d pcap_loop (libpcap.so.0.8 +
0xfd1d)
                #5  0x00005641638a8e5b main_pads (pads + 0x2e5b)
                #6  0x00005641638a847b main (pads + 0x247b)
                #7  0x00007fa6dbc3718a __libc_start_call_main
(libc.so.6 + 0x2718a)
                #8  0x00007fa6dbc37245 __libc_start_main_impl
(libc.so.6 + 0x27245)
                #9  0x00005641638a84b1 _start (pads + 0x24b1)
                ELF object binary architecture: AMD x86-64


-- 
Tim McConnell <tmcconnell168@gmail.com>

On Tue, 2022-09-27 at 10:32 +0200, Bernhard Übelacker wrote:
> Hello Tim,
> I tried to have a look at those two dmesg lines and it seems
> they point to the function print_arp_asset_screen, line 115 [1],
> where parameter rec is dereferenced unconditionally.
> 
> However, if it would be possible to install systemd-coredump then
> a backtrace of those crashes should be printed to the journal.
> This would give a way better information as the two dmesg lines
> alone,
> as it would also show the functions calling print_arp_asset_screen
> and therefore leading to the crash.
> 
> The link [2] might give some more hints to collect
> more information for the maintainer.
> 
> Kind regards,
> Bernhard
> 
> 
> [1]
> https://sources.debian.org/src/pads/1.2-13/src/output/output-screen.c/#L115
>      112 print_arp_asset_screen (ArpAsset *rec)
>      113 {
>      114     /* Print to Screen */
>      115     if(rec->mac_resolved != NULL) {
>      116        fprintf(stdout, "[*] Asset Found:  IP Address - %s /
> MAC Address - %s (%s)\n",
> 
> [2] https://wiki.debian.org/HowToGetABacktrace


Reply to: