From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark Kettenis To: ac131313@cygnus.com Cc: gdb@sourceware.cygnus.com, gdb-patches@sourceware.cygnus.com Subject: Re: [MAINT] x86 maintainers ..... Date: Sat, 01 Apr 2000 00:00:00 -0000 Message-id: <200003012340.e21Ne6o00157@delius.kettenis.local> References: <38BCA2B9.3BDE66AD@cygnus.com> X-SW-Source: 2000-q1/msg00482.html Date: Wed, 01 Mar 2000 15:55:21 +1100 From: Andrew Cagney Hello, I'd like to put forward the following: x86 target Mark Kettenis kettenis@gnu.org GNU/Linux/x86 native & host Jim Blandy jimb@cygnus.com Mark Kettenis kettenis@gnu.org No problems with those. I'll start working on those once you've added them to the MAINTAINERS file :-). Mark >From ac131313@cygnus.com Sat Apr 01 00:00:00 2000 From: Andrew Cagney To: GDB Discussion Cc: GDB Patches Subject: [MAINT] Peter Schauer and Michael Snyder for ``Blanket Write'' maintainers Date: Sat, 01 Apr 2000 00:00:00 -0000 Message-id: <38BDF545.34DB6172@cygnus.com> X-SW-Source: 2000-q1/msg00488.html Content-length: 454 Hello, I'd like to put forward that both: Michael Snyder msnyder@cygnus.com Peter Schauer Peter.Schauer@regent.e-technik.tu-muenchen.de be added to the ``Blanket Write Privs'' maintainers list. Michael Snyder has been hacking continuously on GDB since at least '96 and stands as Red Hat's most experienced GDB developer. In Peter Shauer, case he has been working on improving GDB for much longer (the early '90). Andrew >From ac131313@cygnus.com Sat Apr 01 00:00:00 2000 From: Andrew Cagney To: jtc@redback.com Cc: gdb@sourceware.cygnus.com Subject: Re: command error handling Date: Sat, 01 Apr 2000 00:00:00 -0000 Message-id: <38BD0AD3.7C58E8B2@cygnus.com> References: <5mr9e093zj.fsf@jtc.redbacknetworks.com> X-SW-Source: 2000-q1/msg00471.html Content-length: 1734 "J.T. Conklin" wrote: > > The CLI for the memory region attributes feature I'm working on is > based on displays. Each memory region created is assigned a number, > and can be enabled, disabled, and deleted. > > While stealing the display CLI code, I noticed that when you enable or > disable a non-extant display, a message will be output with printf_- > unfiltered(), but when you do the same thing with delete, GDB calls > error(). The same thing occurs when you attempt to enable/disable/ > delete displays with a non-numeric argument. I'll argue that delete > should behave like enable and disable, that a message be output and > execution should continue. > > The problem with error(), IMHO, is that it's very heavy handed. While > it allows us to avoid the fun of propagating errors up from the lowest > levels of GDB, it also makes it impossible for user defined functions > to detect the failure of a command (that, plus the fact that there are > no command return values, but that's easily remedied by comparision). > Without such a mechanism, the usefulness of scripting is greatly > diminished. I would expect it to much be the same for all extension > languages that may be bound into GDB. > > Is this a (long-term) direction we should be investigating? The consensus last time this was discussed was that code should cleanly unwind the stack stack rather than calling error(). Unfortunatly, eliminating error calls in general is really slow and hard. Even once that is done, there is internal_error() to contend with :-) What people have been doing instead is wrapping calls into GDB so that they always return. The hope is that later, someone else will eliminate the need for the actual wrapper. Andrew >From adenis@EE.UManitoba.CA Sat Apr 01 00:00:00 2000 From: Alexis Denis To: gdb@sourceware.cygnus.com Subject: gdb for java debugging on linuxppc Date: Sat, 01 Apr 2000 00:00:00 -0000 Message-id: <38B1AC30.D93D824E@ee.umanitoba.ca> X-SW-Source: 2000-q1/msg00362.html Content-length: 378 Hi, I'm running - linuxppc Q3 with 2.2.14pre9 kernel - gcc snapshot 20000214 - libgcj snapshot 20000218 - gdb snapshot 000220 I compiled a simple HelloWorld program in java and it runs fine but when I try to run it in the debugger I get: Starting program: /home/adenis/java/HelloWorld Don't know how to run. Try "help target". Any idea why? Thanks, Alexis