Re: Source code analyzer/debugger for X
On May 28, Alex Yukhimets wrote > By the way, where are ddd-dmotif and ddd-smotif packages? They are no more; they were quite out of date (1.4). I don't have motif, and thus cannot build them. > The package ddd (compiled with lesstif) leaves core dumps all over the > place itself. That should change with 2.1-3 (uploaded today), which includes lesstif-specific patches by one of DDD's authors. Also, it is in general advisable to _report_ problems with packages through the bugtracking system, rather than complain about them on debian-user. Greetings, Ray - DDD package maintainer -- POPULATION EXPLOSION Unique in human experience, an event which happened yesterday but which everyone swears won't happen until tomorrow. - The Hipcrime Vocab by Chad C. Mulligan -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Source code analyzer/debugger for X
> > On 27 May 1997 14:43:53 -0700, you wrote: > > >What kinds of free utils are available for analyzing and trying > >to figure out source code? Preferably with a GUI. > > > >-- > >Kevin Hilman -- [EMAIL PROTECTED] > >Sysadmin - Image Computing Systems Lab - U of Washington > >PGP public key at http://icsl.ee.washington.edu/~khilman/ > > > > I've had very good results with ddd and gdb, which should be sufficient > for user-space debugging. For debugging driver code I have used this > combination with gdbstub (ftp://ftp.gcom.com/pub/linux/src/gdbstub/) and > an old 486 as a remote debugger. > > Marty By the way, where are ddd-dmotif and ddd-smotif packages? The package ddd (compiled with lesstif) leaves core dumps all over the place itself. Alex Y. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Source code analyzer/debugger for X
On 27 May 1997 14:43:53 -0700, you wrote: >What kinds of free utils are available for analyzing and trying >to figure out source code? Preferably with a GUI. > >-- >Kevin Hilman -- [EMAIL PROTECTED] >Sysadmin - Image Computing Systems Lab - U of Washington >PGP public key at http://icsl.ee.washington.edu/~khilman/ > I've had very good results with ddd and gdb, which should be sufficient for user-space debugging. For debugging driver code I have used this combination with gdbstub (ftp://ftp.gcom.com/pub/linux/src/gdbstub/) and an old 486 as a remote debugger. Marty -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Source code analyzer/debugger for X
On 27 May 1997, Kevin Hilman wrote: > What kinds of free utils are available for analyzing and trying > to figure out source code? Preferably with a GUI. First of all, there's a command-line debugger, gdb. There are also xxgdb and ddd (and maybe more), which are just X interfaces to gdb (AFAIK, both xxgdb and ddd are available as Debian packages). Don't forget to install lib*-dbg (for simple programs, you'll need only libc5-dbg or libc6-dbg) and compile with -g switch. strip(1)ing an executable or object file removes debugging symbold from it. I think I gave you too much info, Vadik. -- Vadim Vygonets * [EMAIL PROTECTED] * [EMAIL PROTECTED] * Unix admin The fish doesn't think, because the fish knows... everything. -- Arizona Dream -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Source code analyzer/debugger for X
What kinds of free utils are available for analyzing and trying to figure out source code? Preferably with a GUI. -- Kevin Hilman -- [EMAIL PROTECTED] Sysadmin - Image Computing Systems Lab - U of Washington PGP public key at http://icsl.ee.washington.edu/~khilman/ -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
