mailing list of musl libc
 help / color / mirror / code / Atom feed
From: plan9assembler <plan9assembler@gmail.com>
To: musl@lists.openwall.com
Subject: Re: util-linux-2.23 mount segmentation fault error
Date: Sun, 26 May 2013 20:22:49 +0900	[thread overview]
Message-ID: <CAGSZau1_jF2f673Bfbv0cACNn8Pf76aFg_7asSNVXWPukxAiCQ@mail.gmail.com> (raw)
In-Reply-To: <20130526091432.GE31915@port70.net>

[-- Attachment #1: Type: text/plain, Size: 1112 bytes --]

1,2 was fixed, but still gets segfault. 2 trivial, cmp(t,x,y) to
cmp(x,y,t), (thunk,a,b) to (a,b,thunk) etc.
1. _IOR macro for ioctl should use 2U<<30 instead of 2<<30
2. your qsort_r seem to have the wrong prototype

3 is fine by me.
3. settimeofday should follow the bsd declaration

other points need to be checked, i will look at these.
TIA


On Sun, May 26, 2013 at 6:14 PM, Szabolcs Nagy <nsz@port70.net> wrote:

> * plan9assembler <plan9assembler@gmail.com> [2013-05-26 06:34:12 +0900]:
> > Hi, i attached build log, and
>
> there were some minor musl issues:
> _IOR macro for ioctl should use 2U<<30 instead of 2<<30
> settimeofday should follow the bsd declaration
> x86_64 posix types should be long instead of long long
>
> (glibc is not entirely consistent on x86_64:
> the types in user.h use long long)
>
> (i can prepare patches for these)
>
> your qsort_r seem to have the wrong prototype
> (does not match cmp_t)
>
> there are some other problems as well, i'm not sure
> which one trips mount, maybe you should recompile
> musl and util-linux with -O0 -g3 and get a backtrace
> from the crash
>

[-- Attachment #2: Type: text/html, Size: 1651 bytes --]

  reply	other threads:[~2013-05-26 11:22 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-25 15:46 plan9assembler
2013-05-25 16:26 ` Rich Felker
2013-05-25 21:34   ` plan9assembler
2013-05-26  9:14     ` Szabolcs Nagy
2013-05-26 11:22       ` plan9assembler [this message]
2013-05-27 14:05         ` plan9assembler
2013-05-27 14:29           ` Szabolcs Nagy
2013-05-27 21:40             ` plan9assembler
2013-05-29 13:46               ` plan9assembler
2013-05-29 14:11               ` Luca Barbato
2013-05-29 14:32                 ` plan9assembler
2013-05-29 14:41                   ` plan9assembler
2013-05-29 20:04                     ` Szabolcs Nagy
2013-05-29 22:07                       ` plan9assembler
2013-05-29 22:17                         ` plan9assembler
2013-05-30  6:11                           ` plan9assembler
2013-05-30  6:43                             ` Szabolcs Nagy
2013-05-30  7:26                               ` plan9assembler
2013-05-30  8:37                                 ` Szabolcs Nagy
2013-06-01 23:14                                   ` plan9assembler
2013-06-01 23:16                                     ` plan9assembler
2013-06-02  1:50                                     ` John Spencer
2013-06-02 10:55                                       ` plan9assembler
2013-06-02 13:00                                         ` Szabolcs Nagy
2013-06-02 22:02                                           ` plan9assembler

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=CAGSZau1_jF2f673Bfbv0cACNn8Pf76aFg_7asSNVXWPukxAiCQ@mail.gmail.com \
    --to=plan9assembler@gmail.com \
    --cc=musl@lists.openwall.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).