Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Tristan Gingold <gingold@adacore.com>
Cc: jan.kratochvil@redhat.com, gdb-patches@sourceware.org
Subject: Re: [patch] Do not disappoint on "Create a core file of GDB?"
Date: Tue, 12 Jan 2010 19:37:00 -0000	[thread overview]
Message-ID: <836377867l.fsf@gnu.org> (raw)
In-Reply-To: <36BBE15B-5F48-48CD-ABE6-E0D39818EBB2@adacore.com>

> From: Tristan Gingold <gingold@adacore.com>
> Date: Tue, 12 Jan 2010 09:45:29 +0100
> Cc: jan.kratochvil@redhat.com,  gdb-patches@sourceware.org
> 
> 
> On Jan 11, 2010, at 8:15 PM, Eli Zaretskii wrote:
> 
> >> From: Tristan Gingold <gingold@adacore.com>
> >> Date: Mon, 11 Jan 2010 17:07:30 +0100
> >> Cc: gdb-patches@sourceware.org
> >> 
> >> 
> >>> setrlimit is a POSIX function so I hope it does not need autoconf magic:
> >>> 	http://www.opengroup.org/onlinepubs/009695399/functions/setrlimit.html
> >> 
> >> Sure, but windows is not POSIX compliant, so I think you can't avoid some autoconf stuff.
> > 
> > Which "windows" do you have in mind?  If it's Cygwin, I'd imagine it
> > does have setrlimit.  If you are talking about native Windows, then it
> > cannot dump core, anyway, can it?
> 
> Sure.  But it doesn't have setrlimit/getrlimit.

But of course.

In case I wasn't clear, I was actually wondering how come we compile a
source file that's needed for reading and writing core files on a
system where core files aren't supported.  We shouldn't compile it,
and this problem should not exist.


  reply	other threads:[~2010-01-12 19:37 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-11 16:03 Jan Kratochvil
2010-01-11 16:06 ` Tristan Gingold
2010-01-11 16:18   ` Jan Kratochvil
2010-01-11 19:15   ` Eli Zaretskii
2010-01-12  8:44     ` Tristan Gingold
2010-01-12 19:37       ` Eli Zaretskii [this message]
2010-01-15  0:28         ` Jan Kratochvil
2010-01-15  8:24           ` Eli Zaretskii
2010-01-12 16:58 ` Tom Tromey
2010-01-15  0:35   ` Jan Kratochvil
2010-01-30 13:05     ` Mark Kettenis
2010-01-30 14:47       ` Jan Kratochvil
2010-01-31 14:13         ` Mark Kettenis
2010-03-31 13:38           ` Pierre Muller

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=836377867l.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=gingold@adacore.com \
    --cc=jan.kratochvil@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