Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf@redhat.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: Eli Zaretskii <eliz@is.elta.co.il>, gdb@sources.redhat.com
Subject: Re: Just-in-time debugging
Date: Mon, 10 Jun 2002 08:38:00 -0000	[thread overview]
Message-ID: <20020610153837.GJ6201@redhat.com> (raw)
In-Reply-To: <3D04C2F3.7000104@cygnus.com>

On Mon, Jun 10, 2002 at 11:17:07AM -0400, Andrew Cagney wrote:
>>On Sun, 9 Jun 2002, Christopher Faylor wrote:
>>>Unless we want to start documenting things like "How to use ulimit" in
>>>the gdb manual, I don't think it is necessarily appropriate for us
>>>to mention the setting of environment variables for cygwin.
>>
>>The variable is related to GDB, so it sounds appropriate.
>
>Yes.  While not the internal user interface, it definitly very useful 
>and makes someone using GDB's life easier.
>
>Similar to this is knowing how to use GDB to create a stack backtrace.

As I'd mentioned, I think a better example is the unix ulimit command.
A grep of 'ulimit' does not unearth anything in the gdb documentation
directory.  Certainly, if a user wants to create a core file (and why
would you create a core file except for debugging?) they'd need to know
about this.

If you want to start populating the gdb documentation with OS-specific
hints, then I think you should start with linux.

In the meantime, I'm not going to be providing documentation for this.
I don't want to have to worry about modifying the information in two
places when/if we change the CYGWIN environment variable.

cgf


  reply	other threads:[~2002-06-10 15:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-07 17:24 Robin Rowe
2002-06-08 10:26 ` Christopher Faylor
2002-06-08 22:48   ` Eli Zaretskii
2002-06-09  9:30     ` Christopher Faylor
2002-06-09 10:12       ` Eli Zaretskii
2002-06-09 18:47         ` Christopher Faylor
2002-06-09 21:46           ` Eli Zaretskii
2002-06-10  8:17             ` Andrew Cagney
2002-06-10  8:38               ` Christopher Faylor [this message]
2002-06-10 12:10                 ` Eli Zaretskii
2002-06-08 23:17   ` Just-in-time debugging on Linux Robin Rowe

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=20020610153837.GJ6201@redhat.com \
    --to=cgf@redhat.com \
    --cc=ac131313@cygnus.com \
    --cc=eliz@is.elta.co.il \
    --cc=gdb@sources.redhat.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