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: Wed, 29 May 2013 23:32:20 +0900	[thread overview]
Message-ID: <CAGSZau0LQX-GPe+JjLXv28zo7gnUYWNT3ec0b0=SrkfPt9X8fQ@mail.gmail.com> (raw)
In-Reply-To: <51A60C74.6050500@gentoo.org>

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

sorry i don't know how to run bt, and i don't have gdb.

my hdd info:
/dev/sda1  # another linux : LMDE(linux mint based on debian)
/dev/sda2  # swap
/dev/sda3  # bootstrap-linux (using musl-cross as cross compiler instead
of  bootstrap-linux built-in).

and more additional information about latest git-version musl libc. git
pull right now.
result:

# cd util-linux-2.23/.libs
# ./mount /dev/sda1 /mnt
EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)

< 30 - 40  seconds waiting without return to shell>

mount: /mnt: filesystem mounted, but mount(8) failedOperation timed out
// <-- this is weird.
#

and umount gets segfaults randomly..
# umount /mnt
traps: umount[9444] general protection ip:7f9c48e618fb sp:7fff72447b88
error:0 in libc.so[7f9c48e16000+72000]
Segmentation fault.

maybe i should have to build new bootstrap-linux again using new musl libc.







On Wed, May 29, 2013 at 11:11 PM, Luca Barbato <lu_zero@gentoo.org> wrote:

> On 05/27/2013 11:40 PM, plan9assembler wrote:
> > Hi, i am sure but it works for me.
> >
> > actually, it little strange, because,
> > after modification, first time, it getting segfaults,
> > later, it works fine.
>
> A backtrace says anything useful?
>
> lu
>

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

  reply	other threads:[~2013-05-29 14:32 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
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 [this message]
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='CAGSZau0LQX-GPe+JjLXv28zo7gnUYWNT3ec0b0=SrkfPt9X8fQ@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).