Analysing core dump in linux sytem : error
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
We are using a private module to dump a corefile which uses the kernel utility elf_core_dump
in source/fs/binfmt_elf.c
file in kernel source 4.4.52.
Using this module we are getting a core of unlimited size. We use ARM gdb version "GNU gdb (Marvell GCC development 20170123-) 7.10.0.20150918-cvs" to debug a core file.
Using this tool, while opening core file we get the following error:
BFD: Warning: /tmp/filewXU3ip is truncated: expected core file size >= 1684632832, found: 102373296.
warning: Couldn't find general-purpose registers in core file.
warning: Couldn't find general-purpose registers in core file.
PC not available
Could someone please help us to get through this error? Do we need to do some other implementation for this in kernel apart from exporting necessary symbols?
linux core-dump
 |Â
show 4 more comments
up vote
0
down vote
favorite
We are using a private module to dump a corefile which uses the kernel utility elf_core_dump
in source/fs/binfmt_elf.c
file in kernel source 4.4.52.
Using this module we are getting a core of unlimited size. We use ARM gdb version "GNU gdb (Marvell GCC development 20170123-) 7.10.0.20150918-cvs" to debug a core file.
Using this tool, while opening core file we get the following error:
BFD: Warning: /tmp/filewXU3ip is truncated: expected core file size >= 1684632832, found: 102373296.
warning: Couldn't find general-purpose registers in core file.
warning: Couldn't find general-purpose registers in core file.
PC not available
Could someone please help us to get through this error? Do we need to do some other implementation for this in kernel apart from exporting necessary symbols?
linux core-dump
would you include the output ofdf -h
?
â Rui F Ribeiro
Mar 6 at 8:14
1
don't you have a ulimit set on core size? (ulimit -c ), maybe try with ulimit -c unlimited ?
â tonioc
Mar 6 at 8:16
Are you opening it as soon you generate core?
â Rui F Ribeiro
Mar 6 at 8:22
@tonioc ulimit -f also seems to affect core size.
â Rui F Ribeiro
Mar 6 at 8:23
yes the climit is set to unlimited using the option ulimit -c unlimited.
â oxoinfra
Mar 6 at 8:55
 |Â
show 4 more comments
up vote
0
down vote
favorite
up vote
0
down vote
favorite
We are using a private module to dump a corefile which uses the kernel utility elf_core_dump
in source/fs/binfmt_elf.c
file in kernel source 4.4.52.
Using this module we are getting a core of unlimited size. We use ARM gdb version "GNU gdb (Marvell GCC development 20170123-) 7.10.0.20150918-cvs" to debug a core file.
Using this tool, while opening core file we get the following error:
BFD: Warning: /tmp/filewXU3ip is truncated: expected core file size >= 1684632832, found: 102373296.
warning: Couldn't find general-purpose registers in core file.
warning: Couldn't find general-purpose registers in core file.
PC not available
Could someone please help us to get through this error? Do we need to do some other implementation for this in kernel apart from exporting necessary symbols?
linux core-dump
We are using a private module to dump a corefile which uses the kernel utility elf_core_dump
in source/fs/binfmt_elf.c
file in kernel source 4.4.52.
Using this module we are getting a core of unlimited size. We use ARM gdb version "GNU gdb (Marvell GCC development 20170123-) 7.10.0.20150918-cvs" to debug a core file.
Using this tool, while opening core file we get the following error:
BFD: Warning: /tmp/filewXU3ip is truncated: expected core file size >= 1684632832, found: 102373296.
warning: Couldn't find general-purpose registers in core file.
warning: Couldn't find general-purpose registers in core file.
PC not available
Could someone please help us to get through this error? Do we need to do some other implementation for this in kernel apart from exporting necessary symbols?
linux core-dump
edited Mar 6 at 8:58
Stephen Kitt
141k22307367
141k22307367
asked Mar 6 at 8:02
oxoinfra
1
1
would you include the output ofdf -h
?
â Rui F Ribeiro
Mar 6 at 8:14
1
don't you have a ulimit set on core size? (ulimit -c ), maybe try with ulimit -c unlimited ?
â tonioc
Mar 6 at 8:16
Are you opening it as soon you generate core?
â Rui F Ribeiro
Mar 6 at 8:22
@tonioc ulimit -f also seems to affect core size.
â Rui F Ribeiro
Mar 6 at 8:23
yes the climit is set to unlimited using the option ulimit -c unlimited.
â oxoinfra
Mar 6 at 8:55
 |Â
show 4 more comments
would you include the output ofdf -h
?
â Rui F Ribeiro
Mar 6 at 8:14
1
don't you have a ulimit set on core size? (ulimit -c ), maybe try with ulimit -c unlimited ?
â tonioc
Mar 6 at 8:16
Are you opening it as soon you generate core?
â Rui F Ribeiro
Mar 6 at 8:22
@tonioc ulimit -f also seems to affect core size.
â Rui F Ribeiro
Mar 6 at 8:23
yes the climit is set to unlimited using the option ulimit -c unlimited.
â oxoinfra
Mar 6 at 8:55
would you include the output of
df -h
?â Rui F Ribeiro
Mar 6 at 8:14
would you include the output of
df -h
?â Rui F Ribeiro
Mar 6 at 8:14
1
1
don't you have a ulimit set on core size? (ulimit -c ), maybe try with ulimit -c unlimited ?
â tonioc
Mar 6 at 8:16
don't you have a ulimit set on core size? (ulimit -c ), maybe try with ulimit -c unlimited ?
â tonioc
Mar 6 at 8:16
Are you opening it as soon you generate core?
â Rui F Ribeiro
Mar 6 at 8:22
Are you opening it as soon you generate core?
â Rui F Ribeiro
Mar 6 at 8:22
@tonioc ulimit -f also seems to affect core size.
â Rui F Ribeiro
Mar 6 at 8:23
@tonioc ulimit -f also seems to affect core size.
â Rui F Ribeiro
Mar 6 at 8:23
yes the climit is set to unlimited using the option ulimit -c unlimited.
â oxoinfra
Mar 6 at 8:55
yes the climit is set to unlimited using the option ulimit -c unlimited.
â oxoinfra
Mar 6 at 8:55
 |Â
show 4 more comments
1 Answer
1
active
oldest
votes
up vote
0
down vote
At a guess you need to write it to filesystem with more space available.
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
At a guess you need to write it to filesystem with more space available.
add a comment |Â
up vote
0
down vote
At a guess you need to write it to filesystem with more space available.
add a comment |Â
up vote
0
down vote
up vote
0
down vote
At a guess you need to write it to filesystem with more space available.
At a guess you need to write it to filesystem with more space available.
answered Mar 6 at 8:17
Timothy Baldwin
1653
1653
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f428436%2fanalysing-core-dump-in-linux-sytem-error%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
would you include the output of
df -h
?â Rui F Ribeiro
Mar 6 at 8:14
1
don't you have a ulimit set on core size? (ulimit -c ), maybe try with ulimit -c unlimited ?
â tonioc
Mar 6 at 8:16
Are you opening it as soon you generate core?
â Rui F Ribeiro
Mar 6 at 8:22
@tonioc ulimit -f also seems to affect core size.
â Rui F Ribeiro
Mar 6 at 8:23
yes the climit is set to unlimited using the option ulimit -c unlimited.
â oxoinfra
Mar 6 at 8:55