similar to: [PATCH]Add address overflow check

On 09 February 2018 15:56 Jean-Marc Valin wrote: > Pointers are unsigned so this shouldn't be an issue. I suspect you're > being hit by something else. That or your compiler is really broken. I don't know how important it is in this case (probably pretty minor) but in general Ruikai's right. It doesn't matter that pointers are unsigned; that fact that a pointer could

Pointers are unsigned so this shouldn't be an issue. I suspect you're being hit by something else. That or your compiler is really broken. Cheers, Jean-Marc On 02/09/2018 04:42 AM, Ruikai Liu wrote: > Hi, > > I came into a crash when using 32-bit `speexdec` and found that there's > an address overflow in function `print_comments()`: > >

On Fri, Apr 4, 2008 at 12:19 AM, Jean-Marc Valin <jean-marc.valin at usherbrooke.ca> wrote: > Jahn, Ray (R.) a ?crit : > > > Dear Speex codec community: > > > > I am working on conversion of voice files. I could not figure out how to use speexdec.exe 1.2.3 in piped mode in order to avoid the creation of the potentially large intermediate *.wav or *.pcm files. Any

Yes, I agree that buf_end - buf_start < len_to_check is better. It's the 0xFFFFFFFF overflow that's a cause of concern, not the 0x80000000. That being said, I believe that the length argument in this case can be trusted since it comes from the application and not from the user. Cheers, Jean-Marc On 02/12/2018 05:28 AM, Nicholas Wilson wrote: > On 09 February 2018 15:56 Jean-Marc

Dear Jean-Marc and Peter: Thank you both very much for your time and advice. I did not realize that Lame MP3 code has a -r option (without reading its code). I have tried the suggested command lines verbatim with the added -r option, along with other combination of option settings. I could not figure out how to eliminate the distortion in the result, like voice turning either high or low

Hi there, I want to read all data from a binary file (with package Rstreams). I tried the following function (small piece of code): readdata <- function (file) { # open file s <- openstream(file, "read") # read int values while (s$position <= s$size) { readint(s, 1, 2) -> type [...] } return() } and got the following error: > Error in

Here's a propsed heavy-duty solution for your UTF-8 problems. I'm including a patch in this message, but I'll put the new files on my web site at http://rano.org/tmp/xiph_files.tar.gz I've tested this by running vorbiscomment with and without -DHAVE_ICONV=1 in vorbis-tools/share/Makefile. It seems to work. Changed files: acinclude.m4: Add a test for nl_langinfo(CODESET). This

Hi all, in the last time I've intensively used Rstreams to read and write from binary files. Now I'm wondering if it is possible to use Rsteams functions with gzipped files. But I haven't found the trick: > p1c.gzip <- gzfile("daten/p1c_all.mea.gz", open="rb") > readBin(p1c.gzip, integer(), n=64,size=2) [1] 84 1 400 1 749 0 0 0

Hi everyone, Has anyone written a parser in Java for either the ASCII or binary format produced by save()? I need to parse a single large 2D array that is structured like this: list( "32609_1" = c(-9549.39231289146, -9574.07159324482, ... ), "32610_2" = c(-6369.12526971635, -6403.99620977124, ... ), "32618_2" = c(-2138.29095689061, -2057.9229403233, ... ),

This is just to let people know that I'm going to try to put together a little package of binary file read/write functions for R, along the lines described in my message in r-help. I'm going to do it first in R for Windows using a DLL written in Delphi; I'll let people comment on that, and once the design settles down, I'll redo the external code in C so that it should be portable

Evgeniy, thanks for your help. > You need -eng build because preloading libraries into dalvik vm is not > allowed in user builds. JellyBean includes several bugfixes in the > dynamic loader that asan needs. Do you have the sha1 hashes for any of those patches? I might be able to track down a build that includes them. > Was there any useful output in adb logcat when your program

I was just playing around with the R-streams package, reading in some data from an old experiment we did here, and was again amazed by the flexibility of the R environment. The eaze with wich I was able to generate simple plots of my EEG data made me wonder if someone tried to implement an ERP package. For the non-cognitive scientists ou there: EEG is electrical activity measured from the scalp

I'm trying to write comment writer thing for zinf, because I love the program, but it doesn't fully support ogg. I've found how to read comments, but can't figure how to write them. There has been some discussion about this previously in the archives, but I couldn't find any specifics, only references to code not posted to the list. The api documentation page is (painfully)

You are citing the "Android platform workflow" section, which is about sanitizing components of the Android system itself. For NDK apps, see "Android NDK workflow" in the same document. You need -eng build because preloading libraries into dalvik vm is not allowed in user builds. JellyBean includes several bugfixes in the dynamic loader that asan needs. Was there any useful

Here is a patch to fix the compiler warnings I mentioned earlier. I've removed the byte-order changes that don't make sense. (Thanks Michael for pointing out the error!) As for the byte-order changes, since some output modules don't have the option to set the sample byte-order, I would like to standardize libao and ogg123 on native byte-order. Will this break the ao_wav.c patches

From: http://address-sanitizer.googlecode.com/svn-history/r1624/wiki/Android.wiki > AddressSanitizer is fully supported in AOSP starting with JellyBean release. To run > applications built with ASan you'll need an -eng build of Android. > > To build any part of Android system with ASan, add > LOCAL_ADDRESS_SANITIZER:=true to the appropriate Android.mk. I don't see that

Hi I've found bugs in vorbis-tools and wrote this patch to fix them: 1st part is to fix single-channel flac files. 2nd part fixes a problem with thread race causing lockup if you press Ctrl-C Ctrl-C sets sig_request.cancel, buffer thread exits if it sees sig_request.cancel However, if Ctrl-C was pressed here do { if (nthc-- == 0) { ----------------> Ctrl-C

Hi, so here it is, LZ4 compression method inside btrfs. The patchset is based on top of current Chris'' for-linus + Andi''s snappy implementation + the fixes from Li Zefan. Passes xfstests and stresstests. I haven''t measured performance on wide range of hardware or workloads, rather wanted to publish the patches before I get distracted again. I''d like to ask

Thanks for your help on moving files from S+ to R and on attaching directories. If attaching directories is NOT possible in R, is there any other way to separate objects into different folders or something similar? For example, to keep user functions for multivariate analysis in a different "place" than user functions on time series, or to keep data objects of project_1 in a different

Thanks for your help on moving files from S+ to R and on attaching directories. If attaching directories is NOT possible in R, is there any other way to separate objects into different folders or something similar? For example, to keep user functions for multivariate analysis in a different "place" than user functions on time series, or to keep data objects of project_1 in a different