Arch Linux

Just got another crash a few seconds ago :

[ 801.578380] dhcpcd[758]: segfault at 1003ca0 ip 00007ffb40d200cf sp 00007fff24c4d160 error 4 in libc-2.15.so[7ffb40ca6000+197000]

Some more infos : got crash with networkmanager stable version and with networkmanager from gnome-unstable repository.

Another crash, cannot restart networkmanager, had to shutdown directly from start button, not a really good thing.

http://pastebin.com/xsgQ02wD

Note : linux 3.3.0-1 kernel.

I'm kinda fed up with this bug I'm facing for about a week. Deactivating ipv6 support doesn't change a thing :(

@Frederic: It's only in [testing] since Sunday, so not hardly a week ;-)

Can you open a bug report upstream (http://roy.marples.name/projects/dhcpcd) for this as you seem to be the only one with this problem? Note that 5.5.4-2 is git revision 8316b24.

I mean one week because previous version was also giving me problems. I will reinstall my arch from scratch. Maybe it will help "killing" this bug.

Reinstalled from scratch, still this bug annoying me :(

I have the same bug happening on my system. It is most pronounced after I resume from suspending the system and I can't get on the network until I manually restart dhcpcd.

Here's a dump:

*** glibc detected *** dhcpcd: double free or corruption (fasttop): 0x0000000001a61860 ***
======= Backtrace: =========
/lib/libc.so.6(+0x78e66)[0x7f9a79aa5e66]
dhcpcd[0x40cdd0]
dhcpcd[0x40e597]
dhcpcd[0x4093f0]
dhcpcd[0x411ba7]
dhcpcd[0x411563]
dhcpcd[0x40768f]
dhcpcd[0x40aa6b]
dhcpcd[0x4028a8]
/lib/libc.so.6(__libc_start_main+0xed)[0x7f9a79a4e38d]
dhcpcd[0x402d1d]
======= Memory map: ========
00400000-00419000 r-xp 00000000 08:01 7089693 /sbin/dhcpcd
00619000-0061a000 r--p 00019000 08:01 7089693 /sbin/dhcpcd
0061a000-0061b000 rw-p 0001a000 08:01 7089693 /sbin/dhcpcd
0061b000-0061c000 rw-p 00000000 00:00 0
01a60000-01a82000 rw-p 00000000 00:00 0 [heap]
7f9a795fb000-7f9a79610000 r-xp 00000000 08:01 6556929 /usr/lib/libgcc_s.so.1
7f9a79610000-7f9a79810000 ---p 00015000 08:01 6556929 /usr/lib/libgcc_s.so.1
7f9a79810000-7f9a79811000 rw-p 00015000 08:01 6556929 /usr/lib/libgcc_s.so.1
7f9a79811000-7f9a79828000 r-xp 00000000 08:01 7340050 /lib/libpthread-2.15.so
7f9a79828000-7f9a79a27000 ---p 00017000 08:01 7340050 /lib/libpthread-2.15.so
7f9a79a27000-7f9a79a28000 r--p 00016000 08:01 7340050 /lib/libpthread-2.15.so
7f9a79a28000-7f9a79a29000 rw-p 00017000 08:01 7340050 /lib/libpthread-2.15.so
7f9a79a29000-7f9a79a2d000 rw-p 00000000 00:00 0
7f9a79a2d000-7f9a79bc4000 r-xp 00000000 08:01 7346405 /lib/libc-2.15.so
7f9a79bc4000-7f9a79dc4000 ---p 00197000 08:01 7346405 /lib/libc-2.15.so
7f9a79dc4000-7f9a79dc8000 r--p 00197000 08:01 7346405 /lib/libc-2.15.so
7f9a79dc8000-7f9a79dca000 rw-p 0019b000 08:01 7346405 /lib/libc-2.15.so
7f9a79dca000-7f9a79dce000 rw-p 00000000 00:00 0
7f9a79dce000-7f9a79dd5000 r-xp 00000000 08:01 7340288 /lib/librt-2.15.so
7f9a79dd5000-7f9a79fd4000 ---p 00007000 08:01 7340288 /lib/librt-2.15.so
7f9a79fd4000-7f9a79fd5000 r--p 00006000 08:01 7340288 /lib/librt-2.15.so
7f9a79fd5000-7f9a79fd6000 rw-p 00007000 08:01 7340288 /lib/librt-2.15.so
7f9a79fd6000-7f9a79ff7000 r-xp 00000000 08:01 7349520 /lib/ld-2.15.so
7f9a7a1c1000-7f9a7a1c5000 rw-p 00000000 00:00 0
7f9a7a1f4000-7f9a7a1f6000 rw-p 00000000 00:00 0
7f9a7a1f6000-7f9a7a1f7000 r--p 00020000 08:01 7349520 /lib/ld-2.15.so
7f9a7a1f7000-7f9a7a1f8000 rw-p 00021000 08:01 7349520 /lib/ld-2.15.so
7f9a7a1f8000-7f9a7a1f9000 rw-p 00000000 00:00 0
7fff63fce000-7fff63fef000 rw-p 00000000 00:00 0 [stack]
7fff63fff000-7fff64000000 r-xp 00000000 00:00 0 [vdso]
ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0 [vsyscall]

Sorry, I should have closed this bug, discussion has been happening in  FS#28477 .

Is this with the latest 5.5.6 in [testing]? 5.5.6 contains some fixes that I think fixed it for the original reporter. If it still happens in 5.5.6, please post a comment in  FS#28477 .

I'll close this bug now so we don't have a discussion in two threads (and the upstream dev is involved in the other thread).