Complete.Org: Mailing Lists: Archives: freeciv-dev: July 2002:
[Freeciv-Dev] Re: console cleanup 3 (PR#1749)
Home

[Freeciv-Dev] Re: console cleanup 3 (PR#1749)

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: Petr Baudis <pasky@xxxxxxxxxxx>
Cc: "Per I. Mathisen" <per@xxxxxxxxxxx>, freeciv-dev@xxxxxxxxxxx, bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Freeciv-Dev] Re: console cleanup 3 (PR#1749)
From: Raimar Falke <rf13@xxxxxxxxxxxxxxxxx>
Date: Tue, 16 Jul 2002 15:05:47 +0200

On Tue, Jul 16, 2002 at 02:43:28PM +0200, Petr Baudis wrote:
> Dear diary, on Tue, Jul 16, 2002 at 01:58:20PM CEST, I got a letter,
> where Raimar Falke <rf13@xxxxxxxxxxxxxxxxx> told me, that...
> > On Tue, Jul 16, 2002 at 04:52:28AM -0700, Per I. Mathisen wrote:
> > > On Tue, 16 Jul 2002, Raimar Falke wrote:
> > > > On Mon, Jul 15, 2002 at 07:08:20PM -0700, Per I. Mathisen wrote:
> > > > > This is a reversal of my previous console cleanup patch from December.
> > > > > Instead of fixing rfcstyle, it nixes it. Along with the bathwater 
> > > > > goes the
> > > > > remaining "undocumented" commands "log" and "crash" as well. Also,
> > > >
> > > > I used crash in the past. It should stay.
> > > 
> > > Ok. But can you explain to me how crash is useful? This eludes me.
> > 
> > If you want to inspect some server state you can either add freelogs
> > or crash the server and use gdb. The latter is useful if you want/have
> > to work interactive.
> 
> You can attach gdb to running civserver process, and it's even better as 
> you've
> the civserver still "alive".

But this way the server state isn't saved for a second analysis.

> Or, you can just kill -SEGV <civserver_pid>, can't you? ;)

I can. Never thought of this.

        Raimar

-- 
 email: rf13@xxxxxxxxxxxxxxxxx
 checking for the vaidity of the Maxwell laws on this machine... ok
 checking if e=mc^2... ok
 checking if we can safely swap on /dev/fd0... yes
    -- kvirc 2.0.0's configure 


[Prev in Thread] Current Thread [Next in Thread]