29.07.2015 14:40, SF Markus Elfring пишет:
This is *very* strange. The 'format' parameter should not contain that
"%s:%s:%d" prefix at all, as this cannot work of course because the
argument list doesn't match.
I guess that I wonder also about one of my own programming mistakes here.
Which
On 07/29/2015 01:40 PM, SF Markus Elfring wrote:
>> Do you have *any* local modifications in your tree?
>
> Yes. - It seems that I was bitten by a format string mismatch during
> an attempt to display a few more implementation details for my needs.
>
>
> diff --git a/src/libsystemd/sd-device/dev
> This is *very* strange. The 'format' parameter should not contain that
> "%s:%s:%d" prefix at all, as this cannot work of course because the
> argument list doesn't match.
I guess that I wonder also about one of my own programming mistakes here.
> Which version of systemd are you based on?
la
On 07/29/2015 10:06 AM, SF Markus Elfring wrote:
> Program received signal SIGSEGV, Segmentation fault.
> 0x76fefc78 in vfprintf () from /lib64/libc.so.6
> (gdb) bt full
> #0 0x76fefc78 in vfprintf () from /lib64/libc.so.6
> No symbol table info available.
> #1 0x77016f39
> This should usually generate a coredump.
I have regenerated the current software on my test system.
last commit: 6ad6d61f9ddd58983b075e4fbece30bae46fac37
Sonne:/home/elfring/Projekte/Bau/systemd # systemctl stop systemd-udevd.service
systemd-udevd-kernel.socket systemd-udevd-control.socket &&
On Sat, 25.07.15 18:11, SF Markus Elfring (elfr...@users.sourceforge.net) wrote:
> Hello,
>
> I would like to clarify the setting of device file permissions
> for my needs.
>
> So I extended the debug output at some source code places to see
> also better which lines are executed during my tests
>> Jul 26 15:03:38 Sonne systemd-udevd[5347]: auid=1000 uid=0
>> gid=0 ses=1 pid=5347 comm="systemd-udevd"
>> exe="/home/elfring/Projekte/Bau/systemd/systemd-udevd" sig
>> Jul 26 15:03:38 Sonne kernel: systemd-udevd[5347]: segfault at 438 ip
>> 76fefc78 sp 7fffc6b0 error 4 in
>
On Sun, Jul 26, 2015 at 3:22 PM, SF Markus Elfring
wrote:
>> It should print the backtrace with the location where the error happened.
>
> Unfortunately, no.
>
>
> Sonne:/home/elfring/Projekte/Bau/systemd # systemctl stop
> systemd-udevd.service systemd-udevd-kernel.socket
> systemd-udevd-contro
> It should print the backtrace with the location where the error happened.
Unfortunately, no.
Sonne:/home/elfring/Projekte/Bau/systemd # systemctl stop systemd-udevd.service
systemd-udevd-kernel.socket systemd-udevd-control.socket && gdb systemd-udevd
…
worker [5347] terminated by signal 11 (S
On Sat, Jul 25, 2015 at 6:11 PM, SF Markus Elfring
wrote:
> Hello,
>
> I would like to clarify the setting of device file permissions
> for my needs.
>
> So I extended the debug output at some source code places to see
> also better which lines are executed during my tests.
> I built these extensi
Hello,
I would like to clarify the setting of device file permissions
for my needs.
So I extended the debug output at some source code places to see
also better which lines are executed during my tests.
I built these extensions for calls of the function "log_debug"
on the current source files (la
11 matches
Mail list logo
