From: Mark Kettenis <kettenis@wins.uva.nl>
To: fnasser@cygnus.com
Cc: meissner@cygnus.com, tromey@cygnus.com,
gdb-patches@sourceware.cygnus.com
Subject: Re: GDB needs a --cmdline option
Date: Mon, 08 May 2000 11:16:00 -0000 [thread overview]
Message-ID: <200005081816.e48IGJY06715@delius.kettenis.local> (raw)
In-Reply-To: <3916FBE7.ECD328A5@cygnus.com>
Date: Mon, 08 May 2000 13:39:51 -0400
From: Fernando Nasser <fnasser@cygnus.com>
This is getting a bit off topic, but I couldn't resist to respond :-)
Michael Meissner wrote:
>
> Just as a note, when I was at DG many years ago, the debugger
> group there added a feature where a program could invoke the
> debugger as a child whenever it wanted to be debugged (usually in
> the case for long live processes, especially daemons). I recall
> some people adding such a call to AOS/VS's equivalent of a signal
> handler, so you could just hit ^C to start up the debugger.
>
If you modify abort() do that it will try to activate the debugger
if a certain environment variable is set we could work like MS
stuff (if the idea of mimicking MS offends you, just remember they
probably copied it from someone else, it may have even been from
some Unix variant).
We have something like that on the Hurd :-). When a program gets a
fatal signal (for example as a result of calling abort()), it contacts
a special crash server. This crash server is supposed to do whatever
is appropriate like producing a core dump, but that's not implemented
right now. Instead we suspend the process such that you can attach
GDB to it. The nice thing is that this means that the process is
still mostly intact, including its communication channels with other
processes.
It would be a piece of cake to write a crash server that fires up GDB
for you. The nice thing is that the user can specify what crash
server should be used by using an environment variable. So you don't
need to be the system administrator to change it.
This would only make sense for foreground jobs though. Daemons are
probably restricted to core files (which is not that bad -- with
the right log facility and a core file one has a great chance to
reproduce the problem on a subsequent debugger controlled run).
The current crash server allows you to specify different actions for
orphaned processes.
However, this doesn't make the command line option unnecessary. If
the process crashed, it may be hard to reconstruct exactly why it
crashed (I have some experience with debugging a broken calloc()
implementation :-().
Mark
From 3diff@gnu.org Mon May 08 11:21:00 2000
From: Brian Youmans <3diff@gnu.org>
To: fnasser@cygnus.com
Cc: dj@delorie.com, gdb-patches@sourceware.cygnus.com
Subject: Re: authorship
Date: Mon, 08 May 2000 11:21:00 -0000
Message-id: <200005081820.OAA20194@delysid.gnu.org>
References: <200005081355.JAA19096@delysid.gnu.org> <3916CE20.774F4438@cygnus.com> <200005081544.LAA19526@delysid.gnu.org> <200005081637.MAA18610@envy.delorie.com> <3916F261.EB8FAD0C@cygnus.com>
X-SW-Source: 2000-05/msg00135.html
Content-length: 148
"et al." sounds like it is a shortened form of the list, but we wouldn't have
the long version anywhere. How about "and others"?
- Brian Y., FSF
From fnasser@cygnus.com Mon May 08 11:47:00 2000
From: Fernando Nasser <fnasser@cygnus.com>
To: Brian Youmans <3diff@gnu.org>
Cc: dj@delorie.com, gdb-patches@sourceware.cygnus.com
Subject: Re: authorship
Date: Mon, 08 May 2000 11:47:00 -0000
Message-id: <39170BA9.687A988E@cygnus.com>
References: <200005081355.JAA19096@delysid.gnu.org> <3916CE20.774F4438@cygnus.com> <200005081544.LAA19526@delysid.gnu.org> <200005081637.MAA18610@envy.delorie.com> <3916F261.EB8FAD0C@cygnus.com> <200005081809.OAA20154@delysid.gnu.org>
X-SW-Source: 2000-05/msg00136.html
Content-length: 973
Brian Youmans wrote:
>
> Are people agreed that it is reasonable to add Stan Shebs as an
> author? (Stan being conveniently on vacation, he won't see this until
> he gets back.) He seems to have been the chief person that I have
> been dealing with about the manual for the past several years.
> Has he been chiefly responsible for the recent additions to the manual,
> such as the gdb/mi chapter?
>
Yes, Stan has maintained it for several years, so my personal opinion is
that he deserves the credit.
The gdb/mi chapter was written by the authors of that interface
(Andrew, Elena and myself). I guess we are some of the "and others" :-)
There are other "and others" authored chapters as well, being 13, 14 and 18
the ones that come to my mind now.
--
Fernando Nasser
Red Hat - Toronto E-Mail: fnasser@cygnus.com
2323 Yonge Street, Suite #300 Tel: 416-482-2661 ext. 311
Toronto, Ontario M4P 2C9 Fax: 416-482-6299
From 3diff@gnu.org Mon May 08 12:12:00 2000
From: Brian Youmans <3diff@gnu.org>
To: fnasser@cygnus.com
Cc: dj@delorie.com, gdb-patches@sourceware.cygnus.com
Subject: Re: authorship
Date: Mon, 08 May 2000 12:12:00 -0000
Message-id: <200005081911.PAA20484@delysid.gnu.org>
References: <200005081355.JAA19096@delysid.gnu.org> <3916CE20.774F4438@cygnus.com> <200005081544.LAA19526@delysid.gnu.org> <200005081637.MAA18610@envy.delorie.com> <3916F261.EB8FAD0C@cygnus.com> <200005081809.OAA20154@delysid.gnu.org> <39170BA9.687A988E@cygnus.com>
X-SW-Source: 2000-05/msg00137.html
Content-length: 442
We should definitely list acknowledgements like that
explicitly in the contributors section: "Thanks go to
George Washington and Abraham Lincoln for contributing the
chapter 'Using GDB on President's Day'" (or something like that.)
Whether we should also put authors on the chapter itself,
I don't know. I don't think that is our usual practice at the FSF.
But, it is not a bad idea. I've asked RMS for his opinion.
- Brian Youmans, FSF
From dan@cgsoftware.com Mon May 08 14:44:00 2000
From: Daniel Berlin <dan@cgsoftware.com>
To: Christopher Blizzard <blizzard@mozilla.org>
Cc: gdb-patches@sourceware.cygnus.com
Subject: Re: [Fwd: gdb patch]
Date: Mon, 08 May 2000 14:44:00 -0000
Message-id: <Pine.LNX.4.10.10005081443280.19102-100000@propylaea.anduin.com>
References: <3916DC7C.D17FE386@mozilla.org>
X-SW-Source: 2000-05/msg00138.html
Content-length: 775
Yes, we talked about it, and that was the general consensus.
However, i tried for about a week to find a way to make this the default,
and still have other things (like - and +) work, with no luck.
So if everyone likes, it can be merged, just not made the default.
On Mon, 8 May 2000, Christopher Blizzard wrote:
> Did anyone merge this in? I thought that the general consensus was that
> it was a good thing.
>
> --Chris
>
> -------- Original Message --------
> Subject: gdb patch
> Date: Mon, 1 May 2000 08:24:52 -0400
> From: "Jim Nance" <jnance@nortelnetworks.com>
> To: blizzard@redhat.com
>
> Hi Chris,
> I have updated my gdb "list -w" patch to work with the gdb from RH
> 6.2.
> Could you pass it on to whereever it might need to go?
>
> Thanks,
>
> Jim
next prev parent reply other threads:[~2000-05-08 11:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.SOL.3.91.1000507154133.21631E-100000@cse.cygnus.com>
2001-09-05 0:15 ` Tom Tromey
[not found] ` <20000508131024.42535@cse.cygnus.com>
[not found] ` <3916FBE7.ECD328A5@cygnus.com>
2000-05-08 11:16 ` Mark Kettenis [this message]
[not found] <Pine.LNX.4.10.10005101250570.18782-100000@abomination.cygnus.com>
[not found] ` <3919C9EA.95DEC4A5@cygnus.com>
2001-09-05 0:15 ` Tom Tromey
[not found] ` <200005111321.JAA13143@indy.delorie.com>
[not found] ` <391AB98E.D80A537@cygnus.com>
2001-09-05 0:15 ` Tom Tromey
[not found] <Pine.SOL.3.91.1000511131403.14281B-100000@cse.cygnus.com>
[not found] ` <391B1780.23185181@cygnus.com>
2001-09-05 0:15 ` Tom Tromey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200005081816.e48IGJY06715@delius.kettenis.local \
--to=kettenis@wins.uva.nl \
--cc=fnasser@cygnus.com \
--cc=gdb-patches@sourceware.cygnus.com \
--cc=meissner@cygnus.com \
--cc=tromey@cygnus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox