Bug 682408 - [abrt] coreutils-8.5-7.fc14: __fpending@got.plt: Process /bin/mv was killed by signal 11 (SIGSEGV)
[abrt] coreutils-8.5-7.fc14: __fpending@got.plt: Process /bin/mv was killed b...
Product: Fedora
Classification: Fedora
Component: coreutils (Show other bugs)
i686 Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Ondrej Vasik
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2011-03-05 04:09 EST by Dave Cross
Modified: 2011-03-06 11:12 EST (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2011-03-06 02:23:01 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: backtrace (1.56 KB, text/plain)
2011-03-05 04:09 EST, Dave Cross
no flags Details

  None (edit)
Description Dave Cross 2011-03-05 04:09:13 EST
abrt version: 1.1.17
architecture: i686
cmdline: mv XML-Feed/ XML-Feed.old
component: coreutils
Attached file: coredump, 421888 bytes
crash_function: __fpending@got.plt
executable: /bin/mv
package: coreutils-8.5-7.fc14
rating: 4
reason: Process /bin/mv was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1299316158
uid: 500

warning: exec file is newer than core file.
[New Thread 20891]
[Thread debugging using libthread_db enabled]
Core was generated by `mv XML-Feed/ XML-Feed.old'.
Program terminated with signal 11, Segmentation fault.
#0  0x080633fa in __fpending@got.plt ()

Thread 1 (Thread 0xb78d7720 (LWP 20891)):
#0  0x080633fa in __fpending@got.plt ()
No symbol table info available.
From        To          Syms Read   Shared Object Library
0x00ad1230  0x00ae2c58  Yes         /lib/libselinux.so.1
0x00994880  0x00998638  Yes         /lib/librt.so.1
0x042df580  0x042e3bb8  Yes         /lib/libacl.so.1
0x042d7de0  0x042da558  Yes         /lib/libattr.so.1
0x007b6c10  0x008d39e4  Yes         /lib/libc.so.6
0x00958a60  0x00959a88  Yes         /lib/libdl.so.2
0x0077f850  0x00796acf  Yes         /lib/ld-linux.so.2
0x00963600  0x0096f4e8  Yes         /lib/libpthread.so.0
$1 = 0x0
No symbol "__glib_assert_msg" in current context.
eax            0x79f62d9d	2046176669
ecx            0x7978ec	7960812
edx            0x78dcf0	7920880
ebx            0x8062d8c	134622604
esp            0xbff5cc58	0xbff5cc58
ebp            0x0	0x0
esi            0xbff5cc84	-1074410364
edi            0x8062d8c	134622604
eip            0x80633fa	0x80633fa <__fpending@got.plt+2>
eflags         0x10202	[ IF RF ]
cs             0x73	115
ss             0x7b	123
ds             0x7b	123
es             0x7b	123
fs             0x0	0
gs             0x33	51
Dump of assembler code for function __fpending@got.plt:
   0x080633f8 <+0>:	lock jno 0x806337b <__ctype_b_loc@got.plt+3>
   0x080633fb <+3>:	add    %al,(%eax)
End of assembler dump.

How to reproduce
1. touch foo
2. mv foo bar
3. [Segmentation fault (core dumped)]
Comment 1 Dave Cross 2011-03-05 04:09:27 EST
Created attachment 482422 [details]
File: backtrace
Comment 2 Ondrej Vasik 2011-03-05 15:05:26 EST
Is that really reliably reproducable on your machine? If so, is there something specific? e.g. exotic filesystem, hardware, working after suspend/hibernate/whatever relevant?
Comment 3 Dave Cross 2011-03-06 02:23:01 EST
It was reproducable for about 24 hours. Then I decided to reboot so see if that fixed it. At that point it became obvious that there was a far bigger problem, The system wouldn't reboot at all. In the end I had to reinstall the system.

Seems fine now. So this bug can probably be closed.
Comment 4 Ondrej Vasik 2011-03-06 11:12:23 EST
Ok, makes sense, I suspect some library coruption ... anyway, thanks for report and response.

Note You need to log in before you can comment on or make changes to this bug.