From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eli Zaretskii To: cgf@redhat.com Cc: gdb@sources.redhat.com Subject: Re: changelog rotation... Date: Mon, 15 Jan 2001 03:13:00 -0000 Message-id: <200101151113.GAA11867@indy.delorie.com> References: <5md7dt7ski.fsf@jtc.redback.com> <3405-Fri12Jan2001111148+0200-eliz@is.elta.co.il> <3A5F02FE.83E5B350@redhat.com> <9791-Fri12Jan2001174626+0200-eliz@is.elta.co.il> <3791-Sat13Jan2001104448+0200-eliz@is.elta.co.il> <200101141137.GAA16367@indy.delorie.com> <20010114131735.G24031@redhat.com> X-SW-Source: 2001-01/msg00084.html > Date: Sun, 14 Jan 2001 13:17:35 -0500 > From: Christopher Faylor > > >I suspect that some of those registered under NT are actually using > >Windows 2000, where long file names _are_ supported, since the > >zip-picker doesn't distinguish between these two versions. > > Haven't long filenames been supported since almost forever on Windows NT? > I use them on a 3.5 system, at least. For native Windows programs, that's true, of course. But DJGPP programs are DOS executables, as far as Windows is concerned, and DOS executables are barred from issuing the Win32 API calls for file access. So DJGPP programs cannot access the long file names except through a special API avail;able to DOS programs (a bunch of functions of Int 21h). That API is not supported by NT versions before 5 (i.e. before W2K). Windows 9X always had it included. The DJGPP library detects this API at startup and automatically switches all library functions to use that API, thereby proividing a transparent support for long file names. >From eliz@delorie.com Mon Jan 15 03:14:00 2001 From: Eli Zaretskii To: fnasser@redhat.com Cc: cgf@redhat.com, gdb@sources.redhat.com Subject: Re: changelog rotation... Date: Mon, 15 Jan 2001 03:14:00 -0000 Message-id: <200101151114.GAA11874@indy.delorie.com> References: <5md7dt7ski.fsf@jtc.redback.com> <3405-Fri12Jan2001111148+0200-eliz@is.elta.co.il> <3A5F02FE.83E5B350@redhat.com> <9791-Fri12Jan2001174626+0200-eliz@is.elta.co.il> <3791-Sat13Jan2001104448+0200-eliz@is.elta.co.il> <200101141137.GAA16367@indy.delorie.com> <20010114131735.G24031@redhat.com> <3A61F1F9.9E83D82C@redhat.com> X-SW-Source: 2001-01/msg00085.html Content-length: 413 > Date: Sun, 14 Jan 2001 13:37:45 -0500 > From: Fernando Nasser > > Do we build gdb natively on a DOS system or is it generated with > --build --host --target on a higher system? It is mostly built natively. Cross-compilation is not something a typical DJGPP user will consider, and even some of the developers use native build environment for whatever packages whose ports they maintain. >From ac131313@cygnus.com Mon Jan 15 04:14:00 2001 From: Andrew Cagney To: GDB Discussion Cc: haberg@matematik.su.se Subject: C++ Q on types Date: Mon, 15 Jan 2001 04:14:00 -0000 Message-id: <3A62E909.554EECBA@cygnus.com> X-SW-Source: 2001-01/msg00086.html Content-length: 1252 Via RMS: > A user (haberg@matematik.su.se) sent me this explanation of a feature > in some other debuggers: > > C++ has makes available various runtime information (RTTI). C++ has a > single one form of a polymorphic variable, or an object which can change > its type at runtime, namely the polymorphic pointer: If one has a class A > and derives from it a class B, then one can write > A* ap = new B(); > The static type pointer to an A named ap now points to a dynamically > allocated B pointer. It means that in the C++ static typing, this is just > an ap pointer, but C++ has mechanism for keeping track of the dynamic > type B, for example, via "virtual functions", or by using C++ RTTI... > > Now to the debugging: If the debugger only handles C++ static typing, it > will show that ap is an A, and will only display that structure of it > (the names in that class and their values). > > But if the debugger handles C++ dynamic data, it will show that the ap is > actually a B, and will show that (the names in that class B and their > values). > > Does GDB have the ability to determine the actual type > of *ap, and display it accordingly? Something for TODO? >From moshaughnessy@quarrytech.com Mon Jan 15 10:43:00 2001 From: "O'Shaughnessy, Mike" To: "'gdb@sourceware.cygnus.com'" Cc: "O'Shaughnessy, Mike" Subject: gdb with HP probes? Date: Mon, 15 Jan 2001 10:43:00 -0000 Message-id: <496A8683261CD211BF6C0008C733261AA25138@email.quarrytech.com> X-SW-Source: 2001-01/msg00087.html Content-length: 817 I haven't seen anything in the FAQs or archives... Is anyone aware of any existing modification to gdb to allow it to be used with HP/Agilent probes (E5900A/E5900B)? We have quite a few probes that we used with the SDS SingleStep debugger with WRS Tornado/gcc 2.7.2. We've upgraded to gcc 2.95.2, which likes to use dwarf along with stabs, and the SingleStep will not work with it for C++ code. I'd like to replace SingleStep with gdb, but we'd really like to use the probes - they connect to the J-TAG connectors on our embedded PowerPC product. thanks! -------------------------------------------------------- Mike O'Shaughnessy Tel (781) 505-8300 x303 Quarry Technologies, Inc. Fax (781) 505-8316 8 New England Executive Park, Burlington, MA 01803 email: moshaughnessy@quarrytech.com