Reproducible while I try to rip a specific disc. On one occasion, it wiped out my ~/.grip file, too. Reproducible: Always Steps to Reproduce: 1. Launch grip 2. Configure grip (if necessary) to rip and encode on insert. (My .grip file will be provided for reference. If you use that, skip this step) 3. Insert disc Actual Results: Fails with a buffer overflow exception. shortcircuit:3@serenity~/mp3 Mon Sep 19 03:58 PM !512 #12 j0 ?0 $ grip 1> grip_stdout 2>grip_error *** buffer overflow detected ***: grip terminated ======= Backtrace: ========= [snip -- see attachments] ======= Memory map: ======== [snip -- see attachments] Expected Results: It should rip and encode the disc, per configuration. It successfully does this for several other discs.
Created attachment 287051 [details] emerge --info
Created attachment 287053 [details] stack trace and memory map from overflow detection. It appears to have assumed an 80-col-wide terminal. While I can repro the error as many times as I like, I couldn't get it to not wrap the stack and map. Also, redirecting 1> (somefile) and 2> (some_other_file) wound up with this information bypassing those files and being sent to the pty.
Created attachment 287055 [details] grip configuration file rename to $HOME/.grip
Created attachment 287057 [details] grip configuration file for lame rename to $HOME/.grip-lame
Created attachment 287095 [details] gdb capture of crash, including "bt full" output. It wasn't able to find the source files for some things, which I don't know the cause for, nor how to fix systemically. (I have -ggdb in my CFLAGS and splitdebug in FEATURES...I'm not averse to globally-applying debugging features. I like better debugging for less effort, personally.)
please recheck with 3.8.1
