I have tried to launch DDD via libtool. It didn't display any source code to me (not even when I explicitly loaded that source file), and said that it didn't contain any code about every object file it touched. I am clueless to why this is so.
Actually I do not want to discuss why DDD would be pathetic or crap, nor why this wouldn't be the fault of Wireshark's setup. What I know is that I am having another open source project on Linux that is built via automake generated make files, and which I can debug just fine with DDD. I don't want to conduct fruitless discussions about whether the Wireshark setup is any good or not either. All I wish to be is to be able to debug it using DDD. > From: [email protected] > Date: Wed, 26 Jan 2011 10:33:42 -0800 > To: [email protected] > Subject: Re: [Wireshark-dev] Eclipse project for Wireshark > > > On Jan 26, 2011, at 9:22 AM, Guy Harris wrote: > > > On Jan 26, 2011, at 1:34 AM, Dietfrid Mali wrote: > > > >> The problem is that Wireshark is launched by a script settings paths and > >> doing whatnot and finally starting Wireshark from some (hidden?!) > >> subfolder. > > > > That's libtool at work. If the GNU project GDB and the GNU project libtool > > can't work together, that's something for the GNU project to fix; if DDD > > can't handle libtool-based projects, that's something for DDD to fix. > > And if it can't handle libtool-based projects, that would be *really* > pathetic: > > http://ftp.gnu.org/gnu/ddd/ANNOUNCE > > "DDD Makefiles use libtool for generic shared library support." > > To run a debugger on an executable built using libtool, you definitely *do* > need to run it with "./libtool --mode=execute {debugger} {args}", but if > > ./libtool --mode=execute ddd wireshark > > doesn't allow DDD to find Wireshark's source files, but > > ./libtool --mode=execute gdb wireshark > > *does* allow GDB to find Wireshark's source files, that's a DDD bug. > > (I couldn't even get Wireshark or TShark to *start* on Ubuntu 9.10 when I > tried running under GDB - it failed to find the symbol wsp_vals_pdu_type_ext > symbol when I ran "./libtool --mode=execute gdb {wireshark,tshark}", but it > *did* find it when I just ran "./wireshark" or "./tshark" - so I wasn't able > to test it with GDB or DDD; libtool strikes again....) > ___________________________________________________________________________ > Sent via: Wireshark-dev mailing list <[email protected]> > Archives: http://www.wireshark.org/lists/wireshark-dev > Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev > mailto:[email protected]?subject=unsubscribe
___________________________________________________________________________ Sent via: Wireshark-dev mailing list <[email protected]> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:[email protected]?subject=unsubscribe
