Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Denis PILAT <denis.pilat@st.com>
To: gdb-patches <gdb-patches@sourceware.org>
Subject: [RFA] [gdb.threads/testsuite] failure while checking backtrace into main
Date: Wed, 31 Jan 2007 19:36:00 -0000	[thread overview]
Message-ID: <45C0C028.1050401@st.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 443 bytes --]

While checking for non-regression in the gdb.threads part of the 
testsuite, I noticed one test fails with gcc4 since the argument of the 
main are removed by the compiler so don't appear when printing backtrace:
FAIL: gdb.threads/pthreads.exp: check backtrace from main thread

Either we can change the .exp file to avoid checking these arguments, or 
we can ensure compiler keeps them as proposed hereby.

-- 
Denis Pilat
STMicroelectronics

[-- Attachment #2: pthreads.c.patch --]
[-- Type: text/plain, Size: 532 bytes --]

2007-01-31  Denis Pilat  <denis.pilat@st.com>

	* gdb.threads/pthreads.c: ensure argc and argv won't be removed by
	a compiler optimization.

Index: testsuite/gdb.threads/pthreads.c
===================================================================
--- testsuite/gdb.threads/pthreads.c	(revision 553)
+++ testsuite/gdb.threads/pthreads.c	(working copy)
@@ -122,6 +122,8 @@ main(argc, argv)
   void (*xxx) ();
   pthread_attr_t attr;
 
+  if (argv);
+  j = argc;
   if (verbose) printf ("pid = %d\n", getpid());
 
   foo (1, 2, 3);

             reply	other threads:[~2007-01-31 19:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-31 19:36 Denis PILAT [this message]
2007-02-02 14:28 ` Denis PILAT
2007-02-02 14:36   ` Daniel Jacobowitz
2007-02-02 15:18     ` Denis PILAT
2007-02-03  1:35       ` Daniel Jacobowitz

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=45C0C028.1050401@st.com \
    --to=denis.pilat@st.com \
    --cc=gdb-patches@sourceware.org \
    /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