From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32325 invoked by alias); 17 Jan 2012 15:03:39 -0000 Received: (qmail 32309 invoked by uid 22791); 17 Jan 2012 15:03:36 -0000 X-SWARE-Spam-Status: No, hits=-2.6 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,TW_DB X-Spam-Check-By: sourceware.org Received: from mail-iy0-f169.google.com (HELO mail-iy0-f169.google.com) (209.85.210.169) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 17 Jan 2012 15:03:22 +0000 Received: by iadj38 with SMTP id j38so3509719iad.0 for ; Tue, 17 Jan 2012 07:03:21 -0800 (PST) Received: by 10.50.160.194 with SMTP id xm2mr17943002igb.18.1326812601346; Tue, 17 Jan 2012 07:03:21 -0800 (PST) Received: from [192.168.1.102] ([125.122.236.24]) by mx.google.com with ESMTPS id 5sm78122591ibe.8.2012.01.17.07.03.18 (version=SSLv3 cipher=OTHER); Tue, 17 Jan 2012 07:03:20 -0800 (PST) Message-ID: <4F158ECD.3090502@gmail.com> Date: Tue, 17 Jan 2012 15:34:00 -0000 From: asmwarrior User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:9.0) Gecko/20111222 Thunderbird/9.0.1 MIME-Version: 1.0 To: Pierre Muller CC: 'Doug Evans' , gdb-patches@sourceware.org, 'Eli Zaretskii' , 'Tom Tromey' Subject: Re: Possible fix for mingw32 directory relocation problems References: <4f143c53.ca3c440a.1d95.ffff9b71SMTPIN_ADDED@mx.google.com> <4f158a75.65ecd80a.69cb.7083SMTPIN_ADDED@mx.google.com> In-Reply-To: <4f158a75.65ecd80a.69cb.7083SMTPIN_ADDED@mx.google.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2012-01/txt/msg00596.txt.bz2 On 2012-1-17 22:49, Pierre Muller wrote: >> Possible patch is attached. >> Can you try it? I don't know that it will fix things, but based on >> what you've said it seems reasonable to try. > I tried it... > But got really into troubles to regenerate configure and config.in using > Cygwin > installation... > I finally discovered gcc-tools-epoch2 cygwin package > that allowed me to successfully regenerate configure and config.in I just use MSYS+autotools 2.68 to generate configure and config.in under src/gdb. I changed one file, see the change: http://sourceware.org/ml/gdb-patches/2012-01/msg00591.html The trick is that MSYS does not supply autoconf version 2.64, they have 2.63 and 2.65, but I'm not sure why 2.64 is skipped. > After that I did recompile and install gdb into e:\pas\fpc-2.7.1 directory > by specifying --prefix=/e/pas/fpc-2.7.1 > (I tested with --preficx=e:/pas/fpc-2.4.4, which worked the same) > > E:\pas\fpc-2.7.1\gdb>cd bin > > E:\pas\fpc-2.7.1\gdb\bin>.\gdb ./gdb > GNU gdb (GDB) 7.4.50.20120117-cvs > Copyright (C) 2012 Free Software Foundation, Inc. > License GPLv3+: GNU GPL version 3 or later > > This is free software: you are free to change and redistribute it. > There is NO WARRANTY, to the extent permitted by law. Type "show copying" > and "show warranty" for details. > This GDB was configured as "i686-pc-mingw32". > For bug reporting instructions, please see: > ... > Reading symbols from E:\pas\fpc-2.7.1\gdb\bin\gdb.exe...done. > (gdb) py print gdb.PYTHONDIR > e:\pas\fpc-2.7.1\gdb\share\gdb/python > (gdb) py >> end > (gdb) q > > E:\pas\fpc-2.7.1\gdb\bin>cd ..\.. > > E:\pas\fpc-2.7.1>cp -Rf gdb ..\fpc-2.6.0 > > E:\pas\fpc-2.7.1>cd ..\fpc-2.6.0\gdb\bin > > E:\pas\fpc-2.6.0\gdb\bin>.\gdb ./gdb > GNU gdb (GDB) 7.4.50.20120117-cvs > Copyright (C) 2012 Free Software Foundation, Inc. > License GPLv3+: GNU GPL version 3 or later > > This is free software: you are free to change and redistribute it. > There is NO WARRANTY, to the extent permitted by law. Type "show copying" > and "show warranty" for details. > This GDB was configured as "i686-pc-mingw32". > For bug reporting instructions, please see: > ... > Reading symbols from E:\pas\fpc-2.6.0\gdb\bin\gdb.exe...done. > (gdb) py print gdb.PYTHONDIR > e:\pas\fpc-2.6.0\gdb\share\gdb/python > (gdb) > > So the basic idea of rebasing gdb/python seems to work, > the next problem is that I never used python scripts > so that I didn't know what else to do to check that this directory is really > functional! There are many python printer related function under the share folder of gdb, the simply one is "info pretty-printer", but there are many other commands. If the gdb's own python script does NOT loaded correctly, when you run "info pretty-printer", gdb will say that there is not such command. asmwarrior ollydbg from codeblocks' forum