Re: xxgdb should get pulled
On Fri, Jan 22, 1999 at 16:34:58 -0500, Daniel Martin wrote:
[my rant deleted]
> I have yet to learn how to navigate this area, and am often surprised
> at how strongly an offhand comment is taken.
Smilies might have helped. In this case, your comment really triggered me. I
seldomly flame, but in this case, I felt it was justified.
> I'm looking closely at Code Medic now. (Though I'm surprised it isn't
> already on the wnpp list)
The problem with Code Medic is that it is fit for "contrib" at best; I don't
recall its license, but it depends on a GUI library that's non-free ("not
for commercial use" IIRC).
Ray
--
Tevens ben ik van mening dat Nederland overdekt dient te worden.
Re: xxgdb should get pulled
"J.H.M. Dassen" <[EMAIL PROTECTED]> writes: > On Thu, Jan 21, 1999 at 11:28:29 -0500, Daniel Martin wrote: > > Is my only other choice for a graphical debugger the "lesstif-induced > > segfault" ddd? > > Glad to see my work is appreciated. Perhaps this is where I need to point > you to the power of having the source? You could e.g. try fixing LessTif > and/or DDD rather than bitch about it, fix xxgdb, package up UPS, gdbtk, > tgdb, or deet; or (if you're not fully on the straight and narrow) use > Motif-linked DDD binaries, or buy Motif and build a Motif-linked DDD for > Debian, or package up KDbg, or Code Medic. Part of the problem of having a development model in which the primary reward for work is ego gratification (assuming one buys all of ESR's "Homesteading the Noosphere") is that developers tend to get emotionally attached to their packages, much in the same way that academics develop an emotional attachment to their theories or results. I have yet to learn how to navigate this area, and am often surprised at how strongly an offhand comment is taken. (I've discovered myself suddenly CC:ed in a thread on the ddd-devel list which is apparently speculating about what this lesstif bug might be - when I get it reproducing reliably, I'll make a real bug report) Yes, I am grateful that DDD exists and is packaged for Debian, and that the form it is packaged in allows me to keep one more non-free package off my system. Yes, I understand that maintaining a package is difficult; the most complicated packaging I have to deal with is mixed Tcl and C code - I don't even want to imagine what is involved in getting ddd, ddd-smotif and ddd-dmotif out of the same source. Also, I appreciate the names of the other debuggers. I'm looking closely at Code Medic now. (Though I'm surprised it isn't already on the wnpp list)
Re: xxgdb should get pulled
On Thu, Jan 21, 1999 at 11:28:29 -0500, Daniel Martin wrote: > Is my only other choice for a graphical debugger the "lesstif-induced > segfault" ddd? Glad to see my work is appreciated. Perhaps this is where I need to point you to the power of having the source? You could e.g. try fixing LessTif and/or DDD rather than bitch about it, fix xxgdb, package up UPS, gdbtk, tgdb, or deet; or (if you're not fully on the straight and narrow) use Motif-linked DDD binaries, or buy Motif and build a Motif-linked DDD for Debian, or package up KDbg, or Code Medic. Ray -- 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
xxgdb should get pulled
This probably isn't necessary, as I just filed an important and a grave bug against the package, but I thought I'd declare that xxgdb should really be pulled. It doesn't work at al in a libc6 environment, it hasn't been uploaded by its ostensible maintainer since bo was in frozen, and the last NMU for it was just a libc6 recompile for hamm. In essence, it doesn't work at all - just segvio's as soon as you open anything. (this is the grave bug) Also, it fails to build from source. (this is the important bug) So this is a last chance for developers who actually use xxgdb to counter my assertion that currently it's just wasted space on the archives. Does _anyone_ use it? Is my only other choice for a graphical debugger the "lesstif-induced segfault" ddd?
