All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] minicom aborts
Date: Tue, 19 Feb 2019 19:35:53 +0100	[thread overview]
Message-ID: <20190219193553.21e11bc2@gmx.net> (raw)
In-Reply-To: <03499d6b-bd94-b080-f5a9-53e6e0422e78@gmx.com>

Hello David,

On Tue, 19 Feb 2019 12:26:43 +0100, David Picard <dplamp@gmx.com> wrote:

> Hello,
> 
> Le 18/02/2019 ? 20:44, Peter Seiderer a ?crit?:
> > Hello David,
> >
> > On Mon, 18 Feb 2019 16:09:41 +0100, "David PICARD" <dplamp@gmx.com> wrote:
> >  
> >> Hello,
> >>   
> >> When I try to start minicom, some test fails, and minicom quits straight away :
> >>
> >> # minicom
> >> minicom: minicom.c: 1041: test_mbswidth: Assertion `mbswidth(e[i].s) == e[i]._mbswidth || mbswidth(e[i].s) == e[i]._mbswidth_kaputt' failed.
> >> Aborted
> >>   
> >> The minicom.c file can be found here :
> >> https://salsa.debian.org/minicom-team/minicom/blob/master/src/minicom.c
> >>   
> >> My only locale is "C".
> >>   
> >> I'm not sure if it's a bug in minicom or if something is missing on my system.  
> > Try to run with enabled printf debug output:
> >
> > 1038      if (0)
> > 1039         printf("%d: mbswidth=%zd\n", i, mbswidth(e[i].s));
> > 1040       assert(mbswidth(e[i].s) == e[i]._mbswidth
> > 1041 	     || mbswidth(e[i].s) == e[i]._mbswidth_kaputt);
> >
> > And take a look which test fails with which value...  
> So I put "if (1)" in line 1038. The test that failed was the 1st. So I 
> commented out the lines with Asian characters at the beginning of the 
> function, but it still failed. Finally, I put a "return" statement at 
> the beginning of the function, and now it works.

I can confirm minicom (without modifications) needs an UTF8 enabled locale
(e.g. LANG=en_US.utf8) to run without the assert...

The function mbswidth() is implemented in common.c ([1]), using
mbstowcs()....

Regards,
Peter

[1] https://salsa.debian.org/minicom-team/minicom/blob/master/src/common.c#L117

> 
> I attached my defconfig.
> >
> > And share your .config/defconfig file...
> >
> > Regards,
> > Peter
> >     
> >>   
> >> - David
> >> _______________________________________________
> >> buildroot mailing list
> >> buildroot at busybox.net
> >> http://lists.busybox.net/mailman/listinfo/buildroot  
> 

  reply	other threads:[~2019-02-19 18:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-18 15:09 [Buildroot] minicom aborts David PICARD
2019-02-18 19:44 ` Peter Seiderer
2019-02-19 11:26   ` David Picard
2019-02-19 18:35     ` Peter Seiderer [this message]
2019-02-20 10:07       ` David Picard
2019-10-21 20:34         ` AndrePinto
2019-10-22 19:21           ` Peter Seiderer

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=20190219193553.21e11bc2@gmx.net \
    --to=ps.report@gmx.net \
    --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.