All of lore.kernel.org
 help / color / mirror / Atom feed
From: Will Wagner <will_wagner@carallon.com>
To: buildroot@busybox.net
Subject: [Buildroot] WebKit - Random-crashes ?
Date: Tue, 20 Mar 2012 12:55:55 +0000	[thread overview]
Message-ID: <4F687E5B.4040600@carallon.com> (raw)
In-Reply-To: <5E5B6DE50FBE44439A352B17D531676C@JohanW7>

On 20/03/2012 12:48, Sagaert Johan wrote:
>
> Hi
>
> Libsoup again ....
> Hmm remember a few weeks ago a got a problem to with libsoup and the networking used from libglib2
>
> The issue i had was :
>
> Run a function from main() ->  function works
> Run the same function from a thread (either pthread or gthread) functions failed : could not connect..
> I traced it down to gsocket.c and then gave up searching...,i have a target date to get the soft ready.
>
> The socket connect() returned with -1 but errno did not contain the error...
> If i had set errno=1234 BEFORE the connect, then after the connect() failed it still contained 1234 ...
> In reality errno should of been set to EINPROGRESS (115)...
> Strange things that i could not explain...

Hi Johan,

This sounds a lot like a linuxthreads errno bug in uClibc. There is an 
open bug report in uClibc somewhere on the issue. If you built your 
toolchain using buildroot then a patch should have been applied 
(uClibc-0.9.32-linuxthreads-errno-fix.patch) but if you built it using 
crosstools-ng then this issue will remain.

Regards
Will

>
> Johan
>
> -----Oorspronkelijk bericht-----
> Van: buildroot-bounces at busybox.net [mailto:buildroot-bounces at busybox.net] Namens Thomas Petazzoni
> Verzonden: dinsdag 20 maart 2012 11:18
> Aan: buildroot at busybox.net
> Onderwerp: Re: [Buildroot] WebKit - Random-crashes ?
>
> Le Tue, 20 Mar 2012 10:50:13 +0100,
> "Vellemans, Noel"<Noel.Vellemans@visionBMS.com>  a ?crit :
>
>> Finally got 'something' running, that is not crashing all the time.
>> What Did I do?
>> A) Reverted back to older-WebKit 1.2.7. : DID NOT HELP (i.o.w
>> WebKit/GtkLauncher still crashes 'random')
>> A) Reverted back to Uclibc 0.9.32.x     : DID NOT HELP.
>> B) Reverted back to glib-2.28.8         : DID NOT HELP.
>> C) reverted to an older version of GTK (2.24.4): DID NOT HELP.
>> D) Reverted back to libsoup-2.32.2 (had to remove glib-networking
>> depends): SEEMS to be STABLE!
>
> Ah, interesting. Then maybe contacting the libsoup developers will be a good idea.
>
> Another option is to try to upgrade libsoup. We have 2.36.1 in Buildroot, the latest one is
> http://ftp.gnome.org/pub/GNOME/sources/libsoup/2.37/libsoup-2.37.92.tar.xz.
>
>> Compiling WebKit (and his depends) takes some time, even on
>> fast-build-machine (some hours in my case).
>> In order to be sure that everything is recompiled/linked correctly, I
>> always wipe the complete 'output' directory.
>> Is there a faster way to do this?
>> {if I do not wipe the output directory I always have leftovers (in
>> /lib, /usr/lib ..... ) ... from previous compile cycle(s).}
>
> If you want to just rebuild *one* component, you can do:
>
> 	rm -rf output/build/<component>-<version>
>
> and do 'make'. But note that it doesn't remove the previous installation from the target directory, the installation of the new
> component version will overwrite the old one, unless the installed files are different, of course.
>
> Another way of speeding up the build is to use an external toolchain if you're not already using. You can also enable the ccache
> feature (be sure to have the latest ccache fixes, otherwise ccache is basically unused).
>
>> I run Gtklauncher in Val grind as suggested, but I get a Lot of
>> 'console'-output from everywhere.
>> For example.... "== Invalid write of size 4" and/or "Address 0x97b6e14
>> is not stack'd, malloc'd or (recently) free'd"
>> Don't know exactly, how valuable this output is ( i.o.w. did not look
>> into the details yet...)
>
> valgrind is a big, big hammer, and for any given large software stack, the number of errors is so huge that it's difficult to find
> out what's going on.
>
> 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
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot


-- 
------------------------------------------------------------------------
Will Wagner                                     will_wagner at carallon.com
Development Manager                      Office Tel: +44 (0)20 7371 2032
Carallon Ltd, Studio G20, Shepherds Building, Rockley Rd, London W14 0DA
------------------------------------------------------------------------

  reply	other threads:[~2012-03-20 12:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-20  9:50 [Buildroot] WebKit - Random-crashes ? Vellemans, Noel
2012-03-20 10:18 ` Thomas Petazzoni
2012-03-20 12:48   ` Sagaert Johan
2012-03-20 12:55     ` Will Wagner [this message]
2012-03-20 13:02       ` Sagaert Johan
2012-03-21 22:12         ` Peter Korsgaard
  -- strict thread matches above, loose matches on Subject: below --
2012-03-16 10:46 Vellemans, Noel

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=4F687E5B.4040600@carallon.com \
    --to=will_wagner@carallon.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.