From: David Carlton <carlton@math.stanford.edu>
To: Andrew Cagney <ac131313@redhat.com>
Cc: "H. J. Lu" <hjl@lucon.org>, "J. Johnston" <jjohnstn@redhat.com>,
Elena Zannoni <ezannoni@redhat.com>, GDB <gdb@sources.redhat.com>
Subject: Re: NPTL thread support
Date: Mon, 12 May 2003 21:18:00 -0000 [thread overview]
Message-ID: <ro1k7cvzwwp.fsf@jackfruit.Stanford.EDU> (raw)
In-Reply-To: <3EC00D8C.1040100@redhat.com>
On Mon, 12 May 2003 17:09:32 -0400, Andrew Cagney <ac131313@redhat.com> said:
>> These are all normal. (I can't speak about the gdb.objc ones.)
> Unless you've got ObjC installed, those are normal as well (it
> should probably be tweaked too, like threads, just fail when the
> compiler dies).
Whoops, you're right: I thought I was seeing different messages, but I
was seeing those FAILs as well. I agree that the current failure mode
for gdb.objc is suboptimal. Though calling gdb_suppress_entire_file
sounds reasonable to me; is there no way to fix it to actually end the
file instead of trying and failing to suppress the tests in the file?
David Carlton
carlton@math.stanford.edu
next prev parent reply other threads:[~2003-05-12 21:18 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-09 9:45 gdb/dwarf-frame.c Roland McGrath
2003-05-09 13:41 ` gdb/dwarf-frame.c Daniel Jacobowitz
2003-05-09 14:10 ` gdb/dwarf-frame.c Elena Zannoni
2003-05-09 14:56 ` NPTL thread support H. J. Lu
2003-05-09 15:44 ` Elena Zannoni
[not found] ` <20030509091522.A2960@lucon.org>
[not found] ` <16059.55278.841645.134311@localhost.redhat.com>
2003-05-11 20:46 ` H. J. Lu
2003-05-12 19:24 ` J. Johnston
2003-05-12 20:08 ` H. J. Lu
2003-05-12 20:15 ` David Carlton
2003-05-12 21:09 ` Andrew Cagney
2003-05-12 21:18 ` David Carlton [this message]
2003-05-12 21:23 ` Daniel Jacobowitz
2003-05-12 20:17 ` Elena Zannoni
2003-05-09 17:01 ` gdb/dwarf-frame.c Andrew Cagney
2003-05-09 17:08 ` gdb/dwarf-frame.c Elena Zannoni
2003-05-09 19:43 ` gdb/dwarf-frame.c Mark Kettenis
2003-05-09 21:19 ` gdb/dwarf-frame.c Roland McGrath
2003-05-09 21:48 ` gdb/dwarf-frame.c Elena Zannoni
2003-05-09 22:17 ` gdb/dwarf-frame.c Roland McGrath
2003-05-09 21:54 ` gdb/dwarf-frame.c Andrew Cagney
2003-05-09 21:58 ` gdb/dwarf-frame.c Daniel Jacobowitz
2003-05-09 22:18 ` gdb/dwarf-frame.c Roland McGrath
2003-05-09 22:28 ` gdb/dwarf-frame.c Andrew Cagney
2003-05-09 22:33 ` gdb/dwarf-frame.c Roland McGrath
2003-05-09 20:32 ` gdb/dwarf-frame.c Roland McGrath
2003-05-09 19:36 ` gdb/dwarf-frame.c Mark Kettenis
2003-05-09 21:34 ` gdb/dwarf-frame.c Roland McGrath
2003-05-09 21:46 ` gdb/dwarf-frame.c Elena Zannoni
2003-05-10 7:07 ` gdb support for Linux vsyscall DSO Roland McGrath
2003-05-10 17:24 ` Andrew Cagney
2003-05-10 18:13 ` Daniel Jacobowitz
2003-05-10 19:42 ` Roland McGrath
2003-05-10 21:49 ` Andrew Cagney
2003-05-12 19:23 ` Andrew Cagney
2003-05-13 2:29 ` Roland McGrath
2003-05-13 16:03 ` Andrew Cagney
2003-05-10 21:28 ` Roland McGrath
2003-05-10 17:55 ` Mark Kettenis
2003-05-10 20:27 ` Roland McGrath
2003-05-11 23:14 ` Mark Kettenis
2003-05-13 1:53 ` Roland McGrath
2003-05-15 21:26 ` Mark Kettenis
2003-05-16 2:25 ` Roland McGrath
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=ro1k7cvzwwp.fsf@jackfruit.Stanford.EDU \
--to=carlton@math.stanford.edu \
--cc=ac131313@redhat.com \
--cc=ezannoni@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=hjl@lucon.org \
--cc=jjohnstn@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).