FS#7728 - dhcpcd 3.1.3-2 crash

Attached to Project: Arch Linux
Opened by Evgenij Vdovin (evdovin) - Thursday, 02 August 2007, 17:30 GMT
Last edited by Tobias Powalowski (tpowa) - Tuesday, 14 August 2007, 12:12 GMT
Task Type Bug Report
Category Packages: Current
Status Closed
Assigned To Tobias Powalowski (tpowa)
Architecture All
Severity Low
Priority Normal
Reported Version 2007.05 Duke
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

# ./dhcpcd -t 30 -h phobos eth0
*** glibc detected *** ./dhcpcd: malloc(): memory corruption (fast): 0x080582f0 ***
======= Backtrace: =========
/lib/libc.so.6[0xb7ee65e6]
/lib/libc.so.6[0xb7ee8d3d]
/lib/libc.so.6(malloc+0x97)[0xb7ee9e47]
./dhcpcd[0x804b871]
./dhcpcd[0x8049560]
./dhcpcd[0x80499c6]
./dhcpcd[0x804b1c5]
./dhcpcd[0x804f299]
/lib/libc.so.6(__libc_start_main+0xe0)[0xb7e96970]
./dhcpcd[0x80494d1]
======= Memory map: ========
08048000-08055000 r-xp 00000000 00:0f 11320 /tmp/dhcpcd
08055000-08056000 rw-p 0000d000 00:0f 11320 /tmp/dhcpcd
08056000-08077000 rw-p 08056000 00:00 0 [heap]
b7d00000-b7d21000 rw-p b7d00000 00:00 0
b7d21000-b7e00000 ---p b7d21000 00:00 0
b7e75000-b7e7f000 r-xp 00000000 08:08 43264 /usr/lib/libgcc_s.so.1
b7e7f000-b7e80000 rw-p 00009000 08:08 43264 /usr/lib/libgcc_s.so.1
b7e80000-b7e81000 rw-p b7e80000 00:00 0
b7e81000-b7fab000 r-xp 00000000 08:07 411 /lib/libc-2.6.so
b7fab000-b7fac000 r--p 0012a000 08:07 411 /lib/libc-2.6.so
b7fac000-b7fae000 rw-p 0012b000 08:07 411 /lib/libc-2.6.so
b7fae000-b7fb2000 rw-p b7fae000 00:00 0
This task depends upon

Closed by  Tobias Powalowski (tpowa)
Tuesday, 14 August 2007, 12:12 GMT
Reason for closing:  Fixed
Comment by Roman Kyrylych (Romashka) - Friday, 03 August 2007, 11:33 GMT
Does dhcpcd 3.1.3-1 work in the same situation?
Comment by Evgenij Vdovin (evdovin) - Friday, 03 August 2007, 18:49 GMT
No! It's not work. In 3.1.3-1 i have observe same behavior.
Then get this bug in 3.1.3-1, i was hope, what 3.1.3-2 will good, but...
Comment by Evgenij Vdovin (evdovin) - Saturday, 04 August 2007, 07:29 GMT
It's working today (3.1.3-2)???!
I understand nothing!
May be it was because my provider?

Comment by Evgenij Vdovin (evdovin) - Saturday, 04 August 2007, 18:16 GMT
I solve this problem by adding -A (Don't do an ARP check on the IP address.) option.
Without -A argument dhcpcd daemon has periodic crashes.
Comment by Tobias Powalowski (tpowa) - Sunday, 12 August 2007, 13:54 GMT
please try new 3.1.4 package they changed something in arp
Comment by Tobias Powalowski (tpowa) - Monday, 13 August 2007, 20:05 GMT
status on this?
Comment by fedde (fedde) - Tuesday, 14 August 2007, 08:19 GMT
I was having the same problems; disabling the ARP check worked as a workaround. The bug seems fixed in version 3.1.4-1.

Loading...