Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Sagaert Johan <sagaert.johan@skynet.be>
To: buildroot@busybox.net
Subject: [Buildroot] core file
Date: Thu, 15 Mar 2012 15:36:35 +0100	[thread overview]
Message-ID: <486BF3F63CBA4E08B41FE14F46199C39@JohanW7> (raw)
In-Reply-To: <20120315141929.1b885c74@skate>

 
Hi

This is the result from a run with no debug symbols
Also tested using ARM926t instead of the Generic Arm, but this makes no difference. (arm926t = Thumb ?)
Since libdl is the last one, could this one be the one causing the segfault ?


# gdb /usr/bin/curl -c /root/core
GNU gdb (GDB) 7.1

[New Thread 600]
Reading symbols from /usr/lib/libcurl.so.4...(no debugging symbols found)...done
.
Loaded symbols for /usr/lib/libcurl.so.4
Reading symbols from /usr/lib/libz.so.1...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libz.so.1
Reading symbols from /lib/libc.so.0...(no debugging symbols found)...done.
Loaded symbols for /lib/libc.so.0
Reading symbols from /usr/lib/libssl.so.1.0.0...(no debugging symbols found)...d
one.
Loaded symbols for /usr/lib/libssl.so.1.0.0
Reading symbols from /usr/lib/libcrypto.so.1.0.0...(no debugging symbols found).
..done.
Loaded symbols for /usr/lib/libcrypto.so.1.0.0
Reading symbols from /lib/libgcc_s.so.1...(no debugging symbols found)...done.
Loaded symbols for /lib/libgcc_s.so.1
Reading symbols from /lib/ld-uClibc.so.0...(no debugging symbols found)...done.
Loaded symbols for /lib/ld-uClibc.so.0
Reading symbols from /lib/libdl.so.0...(no debugging symbols found)...done.
Loaded symbols for /lib/libdl.so.0
Core was generated by `curl'.
Program terminated with signal 11, Segmentation fault.
#0  0x00000000 in ?? ()
(gdb)

-----Oorspronkelijk bericht-----
Van: buildroot-bounces at busybox.net [mailto:buildroot-bounces at busybox.net] Namens Thomas Petazzoni
Verzonden: donderdag 15 maart 2012 14:19
Aan: Sagaert Johan
CC: buildroot at busybox.net
Onderwerp: Re: [Buildroot] core file

Le Thu, 15 Mar 2012 13:17:06 +0100,
"Sagaert Johan" <sagaert.johan@skynet.be> a ?crit :

> # curl
> ELF header=0x40074000
> First Dynamic section entry=0x40083ef0 Scanning DYNAMIC section Done 
> scanning DYNAMIC section

Seeing those messages, seems like you have built your uClibc with too many debugging options.

> Reading symbols from 
> /lib/libc.so.0.../home/johan/buildroot/output/toolchain/gdb-7.1a/gdb/utils.c:1246: internal-error: virtual memory exhausted: can't
allocate 59954836 bytes.

And you have built it with debugging symbols it seems, so its size is way too big to load on your target. Either use
cross-gdb+gdbserver, or don't compile the uClibc with debugging symbols.

Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux development, consulting, training and support.
http://free-electrons.com
_______________________________________________
buildroot mailing list
buildroot at busybox.net
http://lists.busybox.net/mailman/listinfo/buildroot

  reply	other threads:[~2012-03-15 14:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <DC8F7388218A402C9FEADA4D9CC577B3@JohanW7>
2012-03-15  7:00 ` [Buildroot] core file Thomas Petazzoni
2012-03-15 12:17   ` Sagaert Johan
2012-03-15 13:19     ` Thomas Petazzoni
2012-03-15 14:36       ` Sagaert Johan [this message]
2012-03-15 15:52         ` Thomas Petazzoni
2012-03-15 22:46       ` Arnout Vandecappelle

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=486BF3F63CBA4E08B41FE14F46199C39@JohanW7 \
    --to=sagaert.johan@skynet.be \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox