From mint-bounce@lists.fishpool.fi Thu Jan 28 02:35:47 2010 Message-ID: <4B613D26.3000206@freesbee.fr> Date: Thu, 28 Jan 2010 08:30:46 +0100 From: =?ISO-8859-1?Q?Vincent_Rivi=E8re?= User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.9.1.7) Gecko/20100111 Thunderbird/3.0.1 MIME-Version: 1.0 To: mint@lists.fishpool.fi Subject: Re: [MiNT] OT: Debugging Windom Apps References: <4B60C1E1.7050601@atari-source.org> In-Reply-To: <4B60C1E1.7050601@atari-source.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed X-Antivirus: avast! (VPS 100127-1, 27/01/2010), Outbound message X-Antivirus-Status: Clean X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: vincent.riviere@freesbee.fr Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by mail.sparemint.org id o0S7Zle6004052 Mark Duckworth wrote: > Just worth nothing that you cannot debug a windom application unless you > rebuild libwindom with -g -fomit-frame-pointer -O0. I don't know if there is something special in Windom, but normally "-g" is enough to make debug builds. The flag -fomit-frame-pointer should be used for releases, but the frame pointer is useful for gdb, so this option should not be used in debug builds. Then -O0 is the default optimization level, it should not be required. -- Vincent Rivière