public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "eggert at gnu dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/3440] locale.h macros like LC_ALL are not usable in #if
Date: Fri, 10 Nov 2006 19:06:00 -0000	[thread overview]
Message-ID: <20061110190637.5741.qmail@sourceware.org> (raw)
In-Reply-To: <20061031200834.3440.eggert@gnu.org>


------- Additional Comments From eggert at gnu dot org  2006-11-10 19:06 -------
But this patch does not make it harder to debug programs, since it is already
the case that macros like LC_ALL are typically unavailable in the debug info.
<locale.h> has "#define LC_ALL __LC_ALL", and unless you use something like
gcc -g3, gdb won't see the LC_ALL.

If you like, I can rework the patch so that macros like __LC_ALL are
available in the debug info, but I doubt whether any normal users would
care so I don't see the point.

A better possibility is to rework this patch so that LC_ALL is typically
available in the debug info, while still conforming to C99 and POSIX.
This would require changing locale.h as well.  I can submit that patch
if you prefer.

(The patches for math.h and fenv.h -- bug 3439 -- are in a different category;
I'll look at them a bit later.)

-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=3440

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


  parent reply	other threads:[~2006-11-10 19:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-31 20:08 [Bug libc/3440] New: " eggert at gnu dot org
2006-10-31 20:09 ` [Bug libc/3440] " eggert at gnu dot org
2006-11-10 16:24 ` drepper at redhat dot com
2006-11-10 19:06 ` eggert at gnu dot org [this message]
2007-02-17  8:59 ` drepper at redhat dot com
     [not found] <bug-3440-131@http.sourceware.org/bugzilla/>
2012-04-27 10:50 ` jsm28 at gcc dot gnu.org
2012-05-10 12:42 ` jsm28 at gcc dot gnu.org

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=20061110190637.5741.qmail@sourceware.org \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).