From: Nathan Sidwell <nathan@codesourcery.com>
To: gdb-patches@sourceware.org
Subject: Fix gdb.base/define.exp
Date: Thu, 23 Nov 2006 07:45:00 -0000 [thread overview]
Message-ID: <456551AE.6020604@codesourcery.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 442 bytes --]
the define.exp test requires malloc to be in the target executable
whilenospace
evaluation of this expression requires the program to have a function "malloc".
(gdb) FAIL: gdb.base/define.exp: test whilenospace is parsed correctly
This patch forces malloc to be there. ok?
nathan
--
Nathan Sidwell :: http://www.codesourcery.com :: CodeSourcery
nathan@codesourcery.com :: http://www.planetfall.pwp.blueyonder.co.uk
[-- Attachment #2: all.diff --]
[-- Type: text/plain, Size: 793 bytes --]
2006-11-22 Nathan Sidwell <nathan@codesourcery.com>
* gdb.base/break.c (need_malloc): New.
Index: testsuite/gdb.base/break.c
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.base/break.c,v
retrieving revision 1.5
diff -c -3 -p -r1.5 break.c
*** testsuite/gdb.base/break.c 13 Jun 2006 08:46:17 -0000 1.5
--- testsuite/gdb.base/break.c 22 Nov 2006 15:17:42 -0000
*************** extern void marker3 ();
*** 66,71 ****
--- 66,78 ----
extern void marker4 ();
#endif
+ /* We're used by a test that requires malloc, so make sure it is in
+ the executable. */
+ void *need_malloc ()
+ {
+ return malloc (1);
+ }
+
/*
* This simple classical example of recursion is useful for
* testing stack backtraces and such.
next reply other threads:[~2006-11-23 7:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-23 7:45 Nathan Sidwell [this message]
2006-11-28 15:17 ` Daniel Jacobowitz
2006-11-28 16:06 ` Nathan Sidwell
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=456551AE.6020604@codesourcery.com \
--to=nathan@codesourcery.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