... particularly if those "new" things are tech that had been outdated 20 years ago already.
Thanks for the hint.
I fiddled the ddd call directly in a copy of the wireshark invocation script (basically calling ddd ./libs/wireshark), but still couldn't see any source code.
> Date: Tue, 25 Jan 2011 14:19:53 +0100
> From: balint.reczey@xxxxxxxxxxxx
> To: wireshark-dev@xxxxxxxxxxxxx
> Subject: Re: [Wireshark-dev] Eclipse project for Wireshark
>
> ddd .libs/wireshark works for me (on Debian Squeeze).
>
> Learning new things sometimes involves PITA. :-)
>
> Cheers,
> Balint
>
>
> On 01/25/2011 10:02 AM, Dietfrid Mali wrote:
> > I used the call given below, but replaced 'gdb' with 'ddd'. ddd doesn't
> > display any source code though, so there's still something going wrong.
> >
> > This stuff is a PITA. Can't I even use a graphical debugger frontend to
> > debug Wireshark?
> >
> > > Date: Mon, 24 Jan 2011 14:57:41 -0700
> > > From: steve@xxxxxxxxxxxxxxxxxx
> > > To: wireshark-dev@xxxxxxxxxxxxx
> > > Subject: Re: [Wireshark-dev] Eclipse project for Wireshark
> > >
> > > On Mon, Jan 24, 2011 at 06:29:23PM +0100, Dietfrid Mali wrote:
> > >
> > >
> > > > Thanks. I tried that, and the files are indeed compiled with -g -O0,
> > > > but DDD (gdb) doesn't seem to find an program entry point (and
> > > > complains about bash missing on my openSUSE 11.3 box ???).
> > >
> > > When you debug Wireshark from the root build directory, use libtool as
> > > follows:
> > >
> > > libtool --mode=execute gdb ./wireshark
> > >
> > > Otherwise, you'll be debugging the libtool wrapper script called
> > > wireshark (which calls .libs/wireshark after setting up the proper
> > > library paths and such).
> > >
> > > If you wait to debug it until it's installed, the debugging symbols will
> > > be stripped by make install. I can usually debug Wireshark without
> > > needing to turn off optimizations (-O0).
> > >
> > >
> > ___________________________________________________________________________
> > > Sent via: Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
> > > Archives: http://www.wireshark.org/lists/wireshark-dev
> > > Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
> > > mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe
>
> ___________________________________________________________________________
> Sent via: Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
> Archives: http://www.wireshark.org/lists/wireshark-dev
> Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
> mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe
|