• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: GDB problems and version
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: GDB problems and version


  • Subject: Re: GDB problems and version
  • From: Jim Ingham <email@hidden>
  • Date: Thu, 16 Jul 2009 16:14:35 -0700

Ah, I see. That's not all that surprising, the code that reads the dyld shared library information comes from the original NeXT gdb and predated the solib stuff that was added (originally for Solaris, IIRC) so the two are completely separate implementations. Merging those two bits was always a big pain when we did imports FROM the FSF codebase, so I wouldn't be at all surprised if nobody bothered to merge that stuff back in.

The code would be in the files

src/gdb/macosx/macosx-nat-dyld*.{c,h}

You could look into your built FSF tree to see if any of those files are present and if they are getting built. If not, then you're a ways from being able to see any shared library information in the FSF tree, and things in general aren't going to work all that well. If they are present & getting built, then maybe something is just not wired up correctly, and if you're willing to dig into the gdb sources you could fix it...

When we did merges from the FSF sources onto our fork - back when we were still doing that - it generally took us a couple of weeks to a month to do the merge & make the merged sources work at all, and then a couple of months on and off to find most of the bugs introduced by the merge. And that was when we were merging fairly frequently. If you don't care about using Xcode you could reduce some of the complexity by removing all our additions to the MI & varobj code. Still, it is a non-trivial job.

Good luck,

Jim

On Jul 16, 2009, at 3:03 PM, Christian Thalinger wrote:

Jim Ingham wrote:
Yeah, something is screwy then.  If you do something like:

$ gdb
...
(gdb) attach Mail
...
(gdb) info sharedlibrary

(substitute any other normal running app for Mail) do you get lots of
shared libraries?

Please keep in mind that I'm talking about the FSF GDB. With Apple's GDB shared libraries are working, just not the problem I described.

-- Christian

_______________________________________________ Do not post admin requests to the list. They will be ignored. Xcode-users mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
  • Follow-Ups:
    • Re: GDB problems and version
      • From: Christian Thalinger <email@hidden>
    • Re: GDB problems and version
      • From: Jonas Maebe <email@hidden>
References: 
 >GDB problems and version (From: Christian Thalinger <email@hidden>)
 >Re: GDB problems and version (From: Christian Thalinger <email@hidden>)
 >Re: GDB problems and version (From: Jim Ingham <email@hidden>)
 >Re: GDB problems and version (From: Christian Thalinger <email@hidden>)
 >Re: GDB problems and version (From: Jim Ingham <email@hidden>)
 >Re: GDB problems and version (From: Christian Thalinger <email@hidden>)

  • Prev by Date: Re: GDB & static const variables
  • Next by Date: Re: Changes to the layout of a .xclassmodel file are not persistent
  • Previous by thread: Re: GDB problems and version
  • Next by thread: Re: GDB problems and version
  • Index(es):
    • Date
    • Thread