bug-gettext
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [bug-gettext] Silent crash when processing some Scheme's bytevectors


From: Florent.Angly
Subject: Re: [bug-gettext] Silent crash when processing some Scheme's bytevectors
Date: Wed, 16 May 2018 08:39:23 +0000

Fantastic, thank you Bruno.
Best,
Florent

-----Urspr√ľngliche Nachricht-----
Von: Bruno Haible [mailto:address@hidden
Gesendet: Montag, 14. Mai 2018 21:05
An: address@hidden
Cc: Angly, Florent CH/BRN
Betreff: [EXT] Re: [bug-gettext] Silent crash when processing some Scheme's 
bytevectors

Hi,

Florent Angly wrote:
> inputFile contains the paths to numerous Scheme source files and the
> xgettext command seems to run fine (no errors reported), but the
> expected pot file is not generated. When inspecting the exit code of
> xgettext, I get the value 127, confirming an abnormal exit. I managed
> to narrow the issue to a single source file that contains SRFI-4/R7RS 
> bytevector statements like: '#u8(0 10 5) .
> Uncommenting these statements with a ';' made the failure disappear.

Thanks for reporting it and for having nailed it down to this particular syntax.
There is indeed a memory management bug here.

> Note that the failure is not systematic. It seems to depend on the position 
> of '#u8(). For example, this works:
>     #(0 10 5)
>    '#(0 10 5)
>     #u8(0 10 5)
>    '#u8(0 10 5)
>     #vu8(0 10 5)
>    '#vu8(0 10 5)

Thanks for mentioning this #vu8 syntax. I wasn't aware of it.

The bug will be fixed, and proper support for #vu8 etc. added in the next 
release.

https://urldefense.proofpoint.com/v2/url?u=http-3A__git.savannah.gnu.org_gitweb_-3Fp-3Dgettext.git-3Ba-3Dcommitdiff-3Bh-3D1e07b4420093afa122a3c42e4c531d2633e5fae1&d=DwICAg&c=iYwH3J27U_MBSsOvqcb8y8L0YvDEWvwF8fJyvC56xZM&r=XQAZT8tjM4yt0E8b2QB3ea70dkXMP8E_HaBGT9oG30A&m=UhTvJZJfbiwVGkckVGWIh2OmZrauRt9Sjj7N7A-roWk&s=u_ybn3OCE5sctWYicHCeXPnzLotjgl8BnPxye_RHLNo&e=

Bruno


________________________________

The information in this e-mail is confidential and may be legally privileged. 
It is intended solely for the addressee. If you are not the intended recipient, 
please destroy the message and notify us immediately. Any disclosure, copying 
or distribution of the message is prohibited and may be unlawful.

CSL Behring AG
Switzerland



reply via email to

[Prev in Thread] Current Thread [Next in Thread]