Hi Bernhard,
Well that explains that then, I didn't change anything to pin to the
patched version.
In that case it was fixed and I broke it.
Hopefully the patch will be part of a future release and it'll be
peachy again.
Thanks for explaining what happened.
--
Tim McConnell
On Fri,
Am 23.03.23 um 17:38 schrieb Tim McConnell:
Bernhard,
Just cause I said it was fixed this happens to show up in journalctl:
systemd-coredump[3614]: Process 1704 (pads) of user 0 dumped core.
Bernhard,
Just cause I said it was fixed this happens to show up in journalctl:
systemd-coredump[3614]: Process 1704 (pads) of user 0 dumped core.
Module
libsystemd.so.0 from deb
control: tags -1 +patch
Hello Tim,
nice to hear it helps. Therefore adding the patch tag.
Kind regards,
Bernhard
Am 21.03.23 um 17:53 schrieb Tim McConnell:
Hi Bernhard,
I believe the patch has fixed the issue. I haven't seen any messages
about psad since installing the patch.
Thanks so
Hi Bernhard,
I believe the patch has fixed the issue. I haven't seen any messages
about psad since installing the patch.
Thanks so much for the fix & patience with me.
--
Tim McConnell
On Wed, 2023-03-15 at 12:10 +0100, Bernhard Übelacker wrote:
> Am 26.02.23 um 16:47 schrieb Tim
Hi Benhard,
Okay patch installed, the output is in the attached file.
I was already on 1.2-14 so we'll see if the patch helped or if it was
needed by me.
--
Tim McConnell
On Wed, 2023-03-15 at 12:10 +0100, Bernhard Übelacker wrote:
> Am 26.02.23 um 16:47 schrieb Tim McConnell:
>
> > Hi
Am 26.02.23 um 16:47 schrieb Tim McConnell:
Hi Bernhard,
The delay is fine, I'm sure it takes a minute to figure it out ;-) and
no I didn't have anything other than defaults for GDB set. I'm not a
programmer so I don't know all the tricks to GDB or when is best to
use them. With that said,
On Sun, 2023-02-26 at 16:03 +0100, Bernhard Übelacker wrote:
> Am 08.02.23 um 19:31 schrieb Tim McConnell:
> > Opppss I thought I had, here it is.
> > bt full
>
>
> Hello Tim,
> sorry for the delay. For some reason the debug information
> for libpcap.so.0.8 was missing in your backtrace (was the
Am 08.02.23 um 19:31 schrieb Tim McConnell:
Opppss I thought I had, here it is.
bt full
Hello Tim,
sorry for the delay. For some reason the debug information
for libpcap.so.0.8 was missing in your backtrace (was the
DEBUGINFOD_URLS variable set in that console?).
But I guess I could fill in
Opppss I thought I had, here it is.
bt full
#0 0x5641638af954 in print_arp_asset_screen (rec=0x2a)
at ./src/output/output-screen.c:115
No locals.
#1 0x5641638af6f0 in print_arp_asset (ip_addr=...,
mac_addr=0x7fa6db692384 "") at ./src/output/output.c:210
head =
Am 08.02.23 um 18:42 schrieb Tim McConnell:
Hi Bernhard,
Okay I did that. Let me know if that was of any use.
Hello Tim,
could you send the actual output below the `bt full`?
Kind regards,
Bernhard
Hi Bernhard,
Okay I did that. Let me know if that was of any use.
--
Tim McConnell
On Wed, 2023-02-08 at 16:16 +0100, Bernhard Übelacker wrote:
> bt full
Hello Tim,
thanks, that is good helpful information, but as long the core file
might be in the system, could you execute following commands:
export DEBUGINFOD_URLS="https://debuginfod.debian.net;
coredumpctl gdb 1546
(gdb) bt full
This will enable gdb to download needed debug symbol
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
Hi Bernhard,
I guess there was an upgrade that resolved the issue. I no longer see
any errors for PADS. I guess it could be called an "undocumented
feature" of the upgrade?
Anyway this can be closed as resolved.
Thanks!
--
Tim McConnell
On Tue, 2022-09-27 at 10:32 +0200, Bernhard
Hi Bernhard,
Installed and read the link. I'll see if I can get more useful
information for the maintainer. Thanks for the suggestions on how to
get it.
--
Tim McConnell
On Tue, 2022-09-27 at 10:32 +0200, Bernhard Übelacker wrote:
> if it would be possible to install systemd-coredump then
>
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
Package: pads
Version: 1.2-13
Severity: important
Dear Maintainer,
In dmesg I noticed this:
[87486.873713] pads[2092050]: segfault at 3a ip 5569c2dadb64 sp
7ffc6ce82ed0 error 4 in pads[5569c2da6000+9000]
[87486.873733] Code: 23 00 00 be 01 00 00 00 0f b7 c9 e8 46 85 ff ff 58 31 c0
5a 5b
18 matches
Mail list logo
