Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Curl : Segmentation Fault
Date: Thu, 15 Mar 2012 07:59:04 +0100	[thread overview]
Message-ID: <20120315075904.1e5493e9@skate> (raw)
In-Reply-To: <0DE4C824AF494821A7CBD6732C85F0A6@JohanW7>

Hello,

Le Thu, 15 Mar 2012 01:51:47 +0100,
"Sagaert Johan" <sagaert.johan@skynet.be> a ?crit :

> Thanks for reply, i am getting desperate..
> 
> I am using ARM9 (AT91SAM9260 )

Can you try setting BR2_arm926t=y in your configuration?

I am not sure for what ARM architecture gcc generates code by default
(which is what happens when you use BR2_generic_arm).

> First libsoup causing problems, and when trying to switch to curl something else bites me...
> 
> Should i do a rebuild with strip disabled ?

Yes.

> Should i build a gdb for my target ?

Either that or cross-gdb+gdbserver.

> I tried remote cross debugging with gdbserver but even that causes trouble : debugging a trivial 'Hello world' world using
> uclibc-0.9.33 fails. 
> (breakpoints are just ignored. I don't have that with the 0.9.32)

Argh, ok. It would have been good to report that previously, because it
is quite a big problem if gdbserver doesn't work with uClibc 0.9.33.

Regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

      reply	other threads:[~2012-03-15  6:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-14 16:02 [Buildroot] Curl : Segmentation Fault Sagaert Johan
2012-03-14 19:22 ` Thomas Petazzoni
2012-03-15  0:51   ` Sagaert Johan
2012-03-15  6:59     ` Thomas Petazzoni [this message]

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=20120315075904.1e5493e9@skate \
    --to=thomas.petazzoni@free-electrons.com \
    --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