From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7023 invoked by alias); 12 Jun 2009 22:55:42 -0000 Received: (qmail 7015 invoked by uid 22791); 12 Jun 2009 22:55:42 -0000 X-SWARE-Spam-Status: No, hits=-2.6 required=5.0 tests=BAYES_00 X-Spam-Check-By: sourceware.org Received: from mo-p00-ob.rzone.de (HELO mo-p00-ob.rzone.de) (81.169.146.162) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 12 Jun 2009 22:55:32 +0000 X-RZG-AUTH: :O2kGeEG7b/pS1E6gSHOyjPKyNsg/5l1He+DzFS97kzBIQZntwXMwU3PbSEhSHlg= X-RZG-CLASS-ID: mo00 Received: from [192.168.1.5] (200-161-1-30.br.surtec.com [200.161.1.30]) by post.strato.de (klopstock mo25) (RZmta 18.39) with AES128-SHA encrypted ESMTP id 20488fl5CJ3eyr for ; Sat, 13 Jun 2009 00:55:27 +0200 (MEST) Message-Id: From: Dr. Rolf Jansen To: gdb@sourceware.org Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v935.3) Subject: program does not crash when attached to gdbserver Date: Fri, 12 Jun 2009 22:55:00 -0000 X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2009-06/txt/msg00128.txt.bz2 My setup is as follows: gdb/gdbserver built from CVS trunk from today (6.8.50.20090612-cvs) The source were configured and compiled unchanged: gdb was configured as "--host=powerpc-apple-darwin9.7.0 --target=i386- mingw32msvc". gdbserver was configured as "--host=i386-mingw32msvc --target=i386- mingw32msvc". gdb has been compiled by gcc-4.2 on Mac OS X 10.5.7 with the Xcode 3.1.2 toolchain gdbserver has been compiled with a gcc-4.3.1 cross compiler (-- host=powerpc-apple-darwin9.7.0 --target=i386-mingw32msvc) The situation is, that I am trying to debug a huge GUI application for Win32. It has been entirely compiled with said cross-compiler using the options -gdwarf-2, -O0. I can step through each part, so the symbols are there. The problem is that the application crashes consistently after a certain sequence of user interactions if it runs by its own. However, the same binary does not crash, once it is attached to gdbserver, and it does not crash even when continuing with a couple of stress tests beyound the point at which it would have crashed without gdbserver. It would help so much to find the bug if the program would crash into gdb and if gdb could show me the related source code. This usually works quite well, for example when writing to memory at NULL. Perhaps somebody has an idea about what type of bug might cause the behaviour described above. There was a debugger for Mac OS Classic called MacsBug, that had a setting for scrambling the memory, so that accessing released memory would immediately result into a crash. I cannot seem to find a similar feature in gdb. Does gdb have any settings, that I can try? Many thanks in advance for any help. Best regards Rolf Jansen