> The version I'm using has been flawless. John patched the gdb > problem with add-symbol-file a few months ago, which was the main > culprit of multilink debug problems. It was still possible with the > broken version, but required typing in a literal. > > 2.2.90.cvs20030306-3 (debian unstable) > multilink 0.3
If I understand you correctly, I need a later version of gdb in order to use multilink -- gdb has been fixed and multilink (version 0.3) now works as designed. Correct? That causes me some problems. As mentioned earlier in the thread, I've been using Overbeek's patched version of gdb. If I want to attempt to use multilink, I'll have to switch debuggers as well. I'd prefer to get some version of gdb that has Overbeek's patches as well as the add-symbol-file fix you mention. Have the Overbeek patches been merged into the main development code of gdb? Also is there a cygwin binary of a newer gdb available anywhere, or do I have to download source from sourceforge and build it myself? <snipped sample instructions> Thanks for the detailed instructions. If I get a multilink build working again on my project I'll definitely refer back to them. > At that point, everything is good to go. Nothing else special to do > for debugging multiple segments. You can tell if your gdb has the > broken add-symbol-file by whether the load-segments gives an address > of 0 or if it gives a proper address. Since I'm not currently building with multilink, I can't check this yet. But I'm betting that I have the broken one since Overbeek's patches are dated December of 2002. Rick -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
