cgdb-devel Mailing List for the curses debugger (Page 8)
Brought to you by:
bobbybrasko,
crouchingturbo
Menu
▾
▴
cgdb-devel — Development activity -- bug reports, patches, related questions
You can subscribe to this list here.
| 2003 |
Jan
|
Feb
(19) |
Mar
(15) |
Apr
(6) |
May
|
Jun
(13) |
Jul
(8) |
Aug
(15) |
Sep
(43) |
Oct
(14) |
Nov
(9) |
Dec
(3) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
(4) |
Feb
(9) |
Mar
(15) |
Apr
(5) |
May
(1) |
Jun
|
Jul
(12) |
Aug
|
Sep
|
Oct
|
Nov
(3) |
Dec
|
| 2005 |
Jan
(1) |
Feb
|
Mar
(1) |
Apr
(12) |
May
(7) |
Jun
(7) |
Jul
(21) |
Aug
(7) |
Sep
|
Oct
|
Nov
(1) |
Dec
|
| 2006 |
Jan
(3) |
Feb
(2) |
Mar
(5) |
Apr
(2) |
May
(5) |
Jun
(6) |
Jul
|
Aug
(7) |
Sep
|
Oct
(13) |
Nov
|
Dec
(7) |
| 2007 |
Jan
(3) |
Feb
(16) |
Mar
(6) |
Apr
(8) |
May
(7) |
Jun
(19) |
Jul
(14) |
Aug
(23) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2008 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(14) |
Jun
(3) |
Jul
|
Aug
|
Sep
(6) |
Oct
(3) |
Nov
|
Dec
(1) |
| 2009 |
Jan
(4) |
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
(3) |
Jul
(11) |
Aug
|
Sep
(3) |
Oct
|
Nov
|
Dec
(1) |
| 2010 |
Jan
(3) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(2) |
Nov
(8) |
Dec
(1) |
| 2011 |
Jan
|
Feb
(4) |
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2012 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Bob R. <bo...@br...> - 2006-03-02 02:28:06
|
On Wed, Mar 01, 2006 at 08:24:03AM -0500, Peter Kovacs wrote: > I think he's referring to the fact that sourceforge just enabled svn as > a source control option. Exactly. I currently have a choice of continuing to use CVS, or I could switch to using subversion. Bob Rossi |
|
From: Marcel L. <mar...@n-...> - 2006-03-01 13:35:40
|
I dont have to write much but, I use svn since about two years for all my projects and I=B4d never go back to cvs... 2006/3/1, Bob Rossi <bo...@br...>: > Hi all, > > I was thinking about upgrading CGDB to svn instead of using cvs. Any comm= ents? > > Bob Rossi > > > ------------------------------------------------------- > This SF.Net email is sponsored by xPML, a groundbreaking scripting langua= ge > that extends applications into web and mobile media. Attend the live webc= ast > and join the prime developer group breaking into this new coding territor= y! > http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D110944&bid=3D241720&dat= =3D121642 > _______________________________________________ > Cgdb-devel mailing list > Cgd...@li... > https://lists.sourceforge.net/lists/listinfo/cgdb-devel > > |
|
From: Peter K. <pe...@ko...> - 2006-03-01 13:24:14
|
I think he's referring to the fact that sourceforge just enabled svn as a source control option. I'm partial to bitkeeper myself, despite its non-freeness. - Peter On Tue, Feb 28, 2006 at 09:20:43PM -0800, Steve Folta wrote: > > I was thinking about upgrading CGDB to svn instead of using cvs. Any > > comments? >=20 > Isn't that more of a sidegrade than an upgrade? There's quite a lot > of interesting work and experimentation going on in the field of > source-code control right now. Unfortunately that means that there > isn't a consensus about what's best (like there used to be with CVS).=20 > Personally, I'm using tla (a.k.a. GNU Arch), but I'm rooting for bzr > (a.k.a. Bazaar NG). But I'm only using it for my one-man projects, so > I'm really not taking advantage of the things it (and all the other > modern source-code control systems) is best at. (And by "modern", I > more or less mean "distributed".) Darcs and monotone are a couple > others I can think of; I'm sure there are more I'm forgetting about or > haven't heard of. (And then there's svk, an attempt to graft > distributedness onto svn.) >=20 >=20 > ------------------------------------------------------- > This SF.Net email is sponsored by xPML, a groundbreaking scripting langua= ge > that extends applications into web and mobile media. Attend the live webc= ast > and join the prime developer group breaking into this new coding territor= y! > http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=110944&bid$1720&dat=121642 > _______________________________________________ > Cgdb-devel mailing list > Cgd...@li... > https://lists.sourceforge.net/lists/listinfo/cgdb-devel |
|
From: Steve F. <st...@fo...> - 2006-03-01 05:20:46
|
> I was thinking about upgrading CGDB to svn instead of using cvs. Any > comments? Isn't that more of a sidegrade than an upgrade? There's quite a lot of interesting work and experimentation going on in the field of source-code control right now. Unfortunately that means that there isn't a consensus about what's best (like there used to be with CVS).=20 Personally, I'm using tla (a.k.a. GNU Arch), but I'm rooting for bzr (a.k.a. Bazaar NG). But I'm only using it for my one-man projects, so I'm really not taking advantage of the things it (and all the other modern source-code control systems) is best at. (And by "modern", I more or less mean "distributed".) Darcs and monotone are a couple others I can think of; I'm sure there are more I'm forgetting about or haven't heard of. (And then there's svk, an attempt to graft distributedness onto svn.) |
|
From: Bob R. <bo...@br...> - 2006-03-01 04:28:52
|
Hi all, I was thinking about upgrading CGDB to svn instead of using cvs. Any comments? Bob Rossi |
|
From: PayPal <se...@pa...> - 2006-02-25 19:58:49
|
is .When is , . , , and are what made America great!Unlike so many who have made their to us.Now and then, . |
|
From: Bob R. <bo...@br...> - 2006-02-24 03:28:50
|
Hi All, I received a suggestion to have a command in CGDB that would bring you back to the currently executing instruction. This is useful when you start browsing around (maybe even switched files) and want to get back to the currently executing instruction. I was interested in finding out what key, if any, anyone might suggest to do this? Currently, I'm thinking 'p', as in 'program counter', is the best key for this command. Any other ideas? I suppose a problem with this is, it would only work when the inferior is stopped. So, CGDB would really be taking you to the last location it knew the program counter was at (last executing line). Is this an issue? Thanks, Bob Rossi |
|
From: Bob R. <bo...@br...> - 2006-01-23 02:38:28
|
On Fri, Jan 20, 2006 at 09:43:09AM +0100, Robert Lemmen wrote: > On Thu, Jan 19, 2006 at 09:58:27PM -0500, Bob Rossi wrote: > > Robert, where does that leave us with the man page? Do you still need > > that, or do you prefer the info file? Maybe the man page could just > > describe CGDB, along with the command line arguments and then refer the > > user to the info file. > > right, the manual page should describe what it does, the most important > arguments and very basic usage and then refer to the texinfo and pdf > documentation OK, is this acceptable? I used help2man to generate it. What is the appropriate filename that should be used for this file? cgdb.1? cgdb.man? Also, if anyone has any interest, please review the manual for CGDB, which will be released shortly in the next release of CGDB. It is available here: http://brasko.net:81/bob/cgdbdoc/cgdb/ If you have any comments or critism (should be easy to find), please reply here. Thanks, Bob Rossi |
|
From: Robert L. <rob...@se...> - 2006-01-20 08:43:15
|
On Thu, Jan 19, 2006 at 09:58:27PM -0500, Bob Rossi wrote: > Robert, where does that leave us with the man page? Do you still need > that, or do you prefer the info file? Maybe the man page could just > describe CGDB, along with the command line arguments and then refer the= =20 > user to the info file. right, the manual page should describe what it does, the most important arguments and very basic usage and then refer to the texinfo and pdf documentation cu robert --=20 Robert Lemmen http://www.semistable.com=20 |
|
From: Bob R. <bo...@br...> - 2006-01-20 02:58:15
|
On Sun, Aug 14, 2005 at 03:27:57PM +0200, Marcel Lanz wrote: > > Yeah, they are good, however, there is no "man" page or "info" page. So > > when CGDB is installed on systems, there is no way for the user to get > > documentation the way they would normally get documentation. > > at least on Debian, the cgdb man page exists (written by robert lemmen) Hi Everyone, I'm getting very close to releasing .6.0. Among several bug fixes and features, I've finally put together a manual. I would appreciate any feedback I could get. You can view the manual in html form here, http://brasko.net:81/bob/cgdbdoc/cgdb/ However, since it's written in texinfo, I'll probably put up pdf/html/text on the website, and allow info files to be installed on the distributions. As well, :help in the source window will provide the user with the text version of the manual. Robert, where does that leave us with the man page? Do you still need that, or do you prefer the info file? Maybe the man page could just describe CGDB, along with the command line arguments and then refer the user to the info file. Thanks, Bob Rossi |
|
From: Marcel L. <mar...@ds...> - 2005-08-14 13:28:11
|
> Yeah, they are good, however, there is no "man" page or "info" page. So > when CGDB is installed on systems, there is no way for the user to get > documentation the way they would normally get documentation. at least on Debian, the cgdb man page exists (written by robert lemmen) |
|
From: Bob R. <bo...@br...> - 2005-08-13 13:51:37
|
On Fri, Aug 12, 2005 at 05:52:38PM +0200, Marcel Lanz wrote: > > I was under the impression that doxygen was used for documenting the > > internals of a program (the modules and interfaces). I'm interested in > > documenting the User Interface in a Manual style. Does doxygen do this? > You are right. I thought you want to document cgdb for developers. Well, we already kind of use doxygen for the internal manuals. http://cgdb.sourceforge.net/documentation.shtml however, it is really lacking. This is something to improve upon once the interface's become more stable. > Isn't the manual page and online help enough ? Yeah, they are good, however, there is no "man" page or "info" page. So when CGDB is installed on systems, there is no way for the user to get documentation the way they would normally get documentation. Bob Rossi |
|
From: Marcel L. <mar...@ds...> - 2005-08-12 15:52:53
|
> I was under the impression that doxygen was used for documenting the > internals of a program (the modules and interfaces). I'm interested in > documenting the User Interface in a Manual style. Does doxygen do this? You are right. I thought you want to document cgdb for developers. Isn't the manual page and online help enough ? Marcel |
|
From: Bob R. <bo...@br...> - 2005-08-12 15:18:55
|
On Fri, Aug 12, 2005 at 04:49:00PM +0200, Marcel Lanz wrote: > what about doxygen ? >=20 > http://www.stack.nl/~dimitri/doxygen/ I was under the impression that doxygen was used for documenting the internals of a program (the modules and interfaces). I'm interested in documenting the User Interface in a Manual style. Does doxygen do this? Thanks, Bob Rossi |
|
From: Marcel L. <mar...@ds...> - 2005-08-12 14:49:16
|
what about doxygen ? http://www.stack.nl/~dimitri/doxygen/ marcel On Fri, Aug 12, 2005 at 10:24:28AM -0400, Bob Rossi wrote: > Hi all, > > It has been requested several times that CGDB have better documentation. > It is pretty clear to me that this needs to be done, however, until now > I have had no time to dedicate to this. > > Choosing the appropriate documentation formats are pretty important, > since once they are chosen, I doubt I'll have the time to re-write the > documentation in different formats. > > I'm looking into texinfo > http://www.gnu.org/software/texinfo/texinfo.html > and it seems like an appropriate choice. Does anyone have any objections > to this? or perhaps a better recommendation? > > Thanks, > Bob Rossi |
|
From: Bob R. <bo...@br...> - 2005-08-12 14:24:40
|
Hi all, It has been requested several times that CGDB have better documentation. It is pretty clear to me that this needs to be done, however, until now I have had no time to dedicate to this. Choosing the appropriate documentation formats are pretty important, since once they are chosen, I doubt I'll have the time to re-write the documentation in different formats. I'm looking into texinfo http://www.gnu.org/software/texinfo/texinfo.html and it seems like an appropriate choice. Does anyone have any objections to this? or perhaps a better recommendation? Thanks, Bob Rossi |
|
From: Bob R. <bo...@br...> - 2005-08-03 02:26:36
|
On Thu, Jul 28, 2005 at 08:11:33AM +0200, Marcel Lanz wrote: > > The only problem that I noticed, is since readline is packaged > > now, the release size went from 516289 to 2356190. Does anyone see this > > as a major issue? >=20 > Yes. I noticed the accouncement you'll include readline to the > distribution. I didn't know why you have to do that; I thought it would > increase something like 50k or so. >=20 > I don't know why it has to be included, but if your distro is ~2.3 MByte > and was 0.5 MB before, cgdb is around 22% of the whole thing now. >=20 > Personally, I don't like it. Do you ? (really ?) Just for everyone's info, I dropped the patch that packages readline into CGDB. CGDB will not package readline for the next release. Thanks, Bob Rossi |
|
From: Bob R. <bo...@br...> - 2005-07-29 01:37:42
|
On Thu, Jul 28, 2005 at 02:27:51PM +0200, Robert Lemmen wrote: > On Thu, Jul 28, 2005 at 07:57:55AM -0400, Bob Rossi wrote: > > > about readline: i think statically linking against a library like > > > readline is almost always a really bad idea, and i don't quite > > > understand why you would want to do that.=20 > >=20 > > Could you quickly look at my response to Marcel? Does that help explain > > the reasoning? Do you see any benefit from this reasons? >=20 > ok, i see your points, but i still don't think it outweights the > negative effects. Looks like I made an error while creating the tarball. I included in the distro the readline source and build files. When I correct that mistake and remove some of the documentation files, I've got the size of CGDB=20 down to 868K cgdb-0.5.2-cvs.tar.gz instead of 516K cgdb-0.5.2 Does this seem better to everyone? Bob Rossi |
|
From: Robert L. <rob...@se...> - 2005-07-28 12:27:57
|
On Thu, Jul 28, 2005 at 07:57:55AM -0400, Bob Rossi wrote: > > about readline: i think statically linking against a library like > > readline is almost always a really bad idea, and i don't quite > > understand why you would want to do that.=20 >=20 > Could you quickly look at my response to Marcel? Does that help explain > the reasoning? Do you see any benefit from this reasons? ok, i see your points, but i still don't think it outweights the negative effects. > > it is definitely disabled in > > the debian build. the reason against this (apart from binary size, > > memory usage, speed...) is that if there is a bug in the library you can > > fix the library, if it is statically linked you first need to find every > > usage of it, and patch it individually. this happens all the time... >=20 > Yes, this makes sense to me, I was figuring you would use the system > readline, at least for now. What will you do when CGDB depends on the > newest readline? cgdb will depend on readline5 and will only be released together with it. the impact that this has is hard to tell, depends a lot on how fast the next readline release will happebn. if it's soonish and goodish it will be no problem for debian "stable" users as the new readline will then be in testing by the time etch (the next release) freezes. if it takes long to release and/or is very buggy then the new readline will not make it into etch, and therefore cgdb will stay at 0.5.3 (or whatever was hte last pre-new-readline version). i'd bet the former will happen... btw: at least on debian gdb does not statically link against readline, bash does though. cu robert --=20 Robert Lemmen http://www.semistable.com=20 |
|
From: Bob R. <bo...@br...> - 2005-07-28 11:58:08
|
On Thu, Jul 28, 2005 at 10:36:23AM +0200, Robert Lemmen wrote: > On Wed, Jul 27, 2005 at 09:46:28PM -0400, Bob Rossi wrote: > > You can try out cgdb-0.5.3-beta at sf.net/projects/cgdb. There has been > > pretty major changes to the autotools stuff, so that could be a hint to > > all of the package maintainers to make sure there setup still works > > fine. > >=20 > > If there is no complaints, I'll probably release the next version in a > > week or so. > >=20 > > The only problem that I noticed, is since readline is packaged > > now, the release size went from 516289 to 2356190. Does anyone see this > > as a major issue? > about readline: i think statically linking against a library like > readline is almost always a really bad idea, and i don't quite > understand why you would want to do that.=20 Could you quickly look at my response to Marcel? Does that help explain the reasoning? Do you see any benefit from this reasons? > it is definitely disabled in > the debian build. the reason against this (apart from binary size, > memory usage, speed...) is that if there is a bug in the library you can > fix the library, if it is statically linked you first need to find every > usage of it, and patch it individually. this happens all the time... Yes, this makes sense to me, I was figuring you would use the system readline, at least for now. What will you do when CGDB depends on the newest readline? Thanks, Bob Rossi |
|
From: Bob R. <bo...@br...> - 2005-07-28 11:55:05
|
On Thu, Jul 28, 2005 at 08:11:33AM +0200, Marcel Lanz wrote: > > The only problem that I noticed, is since readline is packaged > > now, the release size went from 516289 to 2356190. Does anyone see this > > as a major issue? >=20 > Yes. I noticed the accouncement you'll include readline to the > distribution. I didn't know why you have to do that; I thought it would > increase something like 50k or so. >=20 > I don't know why it has to be included, but if your distro is ~2.3 MByte > and was 0.5 MB before, cgdb is around 22% of the whole thing now. >=20 > Personally, I don't like it. Do you ? (really ?) >=20 > Are there other projects packaging readline ?=20 Yes, many programs do this. For instance, bash and GDB. > What are the reasons ? Programs like GDB patch readline, which is probably the sole reason why they package it. There is 2 reasons that I decided to package readline into CGDB. The first is to make it easier for people to install CGDB on there system. It can be very time consuming to install CGDB on some systems that do not have readline installed by default (especially on a secure system). The second reason is, I've recently submitted several patches to readline, and the next release will have functionality that CGDB needs. So, in order to install CGDB you will need the *latest* release of readline. I figurued *most* users would find it to complicated to get the latest release of readline, install it, and then install CGDB. Do either of these reasons outweigh the source size change to you? Thanks, Bob Rossi |
|
From: Robert L. <rob...@se...> - 2005-07-28 08:36:31
|
On Wed, Jul 27, 2005 at 09:46:28PM -0400, Bob Rossi wrote: > You can try out cgdb-0.5.3-beta at sf.net/projects/cgdb. There has been > pretty major changes to the autotools stuff, so that could be a hint to > all of the package maintainers to make sure there setup still works > fine. >=20 > If there is no complaints, I'll probably release the next version in a > week or so. >=20 > The only problem that I noticed, is since readline is packaged > now, the release size went from 516289 to 2356190. Does anyone see this > as a major issue? hi bob, i tried the new tarball and it does work for me, the only small issue that i did see is that you should run "make clean" in the readline dir when you do the clean run in the main dir as well. about readline: i think statically linking against a library like readline is almost always a really bad idea, and i don't quite understand why you would want to do that. it is definitely disabled in the debian build. the reason against this (apart from binary size, memory usage, speed...) is that if there is a bug in the library you can fix the library, if it is statically linked you first need to find every usage of it, and patch it individually. this happens all the time... i also do agree with marcel that the increase in source size is awkward, but thats less of an issue to me. anyway: it's your call and i don't mind as long as i can turn it off, but= =20 i doubt it's a good idea. cu robert --=20 Robert Lemmen http://www.semistable.com=20 |
|
From: Marcel L. <mar...@ds...> - 2005-07-28 06:11:45
|
> The only problem that I noticed, is since readline is packaged > now, the release size went from 516289 to 2356190. Does anyone see this > as a major issue? Yes. I noticed the accouncement you'll include readline to the distribution. I didn't know why you have to do that; I thought it would increase something like 50k or so. I don't know why it has to be included, but if your distro is ~2.3 MByte and was 0.5 MB before, cgdb is around 22% of the whole thing now. Personally, I don't like it. Do you ? (really ?) Are there other projects packaging readline ? What are the reasons ? |
|
From: Bob R. <bo...@br...> - 2005-07-28 01:46:39
|
Hi all, You can try out cgdb-0.5.3-beta at sf.net/projects/cgdb. There has been pretty major changes to the autotools stuff, so that could be a hint to all of the package maintainers to make sure there setup still works fine. If there is no complaints, I'll probably release the next version in a week or so. The only problem that I noticed, is since readline is packaged now, the release size went from 516289 to 2356190. Does anyone see this as a major issue? Thanks, Bob Rossi |
|
From: Bob R. <bo...@br...> - 2005-07-26 23:56:15
|
On Mon, Jul 25, 2005 at 07:07:09PM -0400, Mike Mueller wrote: > > On Sat, Jul 23, 2005 at 05:49:27AM -0400, Mike Mueller wrote: > > OK, I'll make sure to test this within the next few days. Also, items > > issued to be fixed/resolved on the release schedule for .0.5.3 is below, > > - Merge in temporary breakpoint code and choose a letter for it. > I agree that 't' is the best letter for this. It seems like the tty > option is not used very much since it is often easier to attach to a > terminal-based application running in a separate window. This kind of > stuff definitely underscores the need for user-configurable mappings in > the future... OK, currently it is, - t -> insert into tty window - I -> does nothing - i -> insert into GDB window - T -> open/close tty window I've changed that to - t -> set a temporary breakpoint - I -> insert into tty window - i -> insert into GDB window - T -> open/close tty window Personally, I find it more intuitve. Do you like the change? If so I'll commit it. Thanks, Bob Rossi |
35 messages has been excluded from this view by a project administrator.
