From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14424 invoked by alias); 31 Aug 2012 13:49:02 -0000 Received: (qmail 14407 invoked by uid 22791); 31 Aug 2012 13:49:01 -0000 X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,TW_BJ,TW_IB X-Spam-Check-By: sourceware.org Received: from bromo.med.uc.edu (HELO bromo.med.uc.edu) (129.137.3.146) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 31 Aug 2012 13:48:47 +0000 Received: from bromo.med.uc.edu (localhost.localdomain [127.0.0.1]) by bromo.med.uc.edu (Postfix) with ESMTP id 46287400007; Fri, 31 Aug 2012 09:48:46 -0400 (EDT) Received: (from howarth@localhost) by bromo.med.uc.edu (8.14.3/8.14.3/Submit) id q7VDmjfm020074; Fri, 31 Aug 2012 09:48:45 -0400 Date: Fri, 31 Aug 2012 13:49:00 -0000 From: Jack Howarth To: Tristan Gingold Cc: Kaushik Srenevasan , gdb@sourceware.org Subject: Re: GDB 7.5 on OS X 10.7 Message-ID: <20120831134845.GA20042@bromo.med.uc.edu> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.18 (2008-05-17) 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: 2012-08/txt/msg00102.txt.bz2 On Fri, Aug 31, 2012 at 11:19:18AM +0200, Tristan Gingold wrote: > > On Aug 31, 2012, at 6:37 AM, Kaushik Srenevasan wrote: > > > Is GDB (7.5) known to work on OS X 10.7? I compiled it from GIT with > > all defaults except the prefix but don't seem to be able to get even > > the basic commands (bt, break) to work. > > Yes, it is known to work (I use it every days). However there is still many issues because it is not heavily used. > In particular, I rarely debug dylibs. > > Tristan. Tristan, Sorry to hijack the thread, but what is the status of support for gdb 7.5 in 10.8? It seems that the approach of using... sudo dscl . append /Groups/_developer GroupMembership howarth doesn't allow non-root users to access the mach ports any more. Unless I run fsf-gdb as sudo, I get an error... Unable to find Mach task port for process-id 24007: (os/kern) failure (0x5). (please check gdb is codesigned - see taskgated(8)) Also, even as sudo, I do get some non-fatal warnings from gdb 7.5... % sudo fsf-gdb ./a.out GNU gdb (GDB) 7.5 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 "x86_64-apple-darwin12.2.0". For bug reporting instructions, please see: ... BFD: /Users/howarth/a.out: unknown load command 0x2a BFD: /Users/howarth/a.out: unknown load command 0x28 BFD: /Users/howarth/a.out: unknown load command 0x2b BFD: /Users/howarth/a.out: unknown load command 0x2a BFD: /Users/howarth/a.out: unknown load command 0x28 BFD: /Users/howarth/a.out: unknown load command 0x2b Reading symbols from /Users/howarth/a.out...Reading symbols from /Users/howarth/a.out.dSYM/Contents/Resources/DWARF/a.out...done. done. Are those significant? Jack > > > > > file ~/src/jdk7/build/macosx-x86_64-debug/bin/java > > set args -classpath ~/src/tmp helloworld > > catch load libjvm > > > > Catchpoint 1 > > Inferior loaded > > /Users/ks/src/jdk7/build/macosx-x86_64-debug/lib/server/libjvm.dylib > > 0x00007fff5fc0b269 in ?? () > > (gdb) bt > > #0 0x00007fff5fc0b269 in ?? () > > #1 0x00007fff5fc0b24d in ?? () > > #2 0x00000001000d1a50 in ?? () > > #3 0x00007fff5fc3b560 in ?? () > > #4 0x00000001000d1f20 in ?? () > > #5 0x00007fff5fc0540e in ?? () > > #6 0x0000000101800000 in ?? () > > #7 0x0000000100200300 in ?? () > > #8 0x0000000050403138 in ?? () > > #9 0x00007fff5fc052ea in ?? () > > #10 0x0000000100200260 in ?? () > > #11 0x00000001000d1ae8 in ?? () > > #12 0x0000000000000000 in ?? () > > (gdb) break LRG::set_mask > > Cannot access memory at address 0x141be0 > > > > It looks like break was able to find the symbol's address. The address > > however looks suspect to me. The target (if that matters) is a debug > > build of the OpenJDK. > > > > --- Kaushik