Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@vmware.com>
To: Hui Zhu <teawater@gmail.com>
Cc: Michael Eager <eager@eagercon.com>,
	  Pierre Muller <muller@ics.u-strasbg.fr>,
	 "msnyder@sourceware.org" <msnyder@sourceware.org>,
	  "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: Build failure: src/gdb ChangeLog record.c gcore.c gcore.h
Date: Sun, 25 Oct 2009 18:42:00 -0000	[thread overview]
Message-ID: <4AE49A75.9030007@vmware.com> (raw)
In-Reply-To: <daef60380910250141k4086e4b1taef64052484ec9eb@mail.gmail.com>

Hui Zhu wrote:
> $ ./gdb ./a.exe
> GNU gdb (GDB) 7.0.50.20091025-cvs
> Copyright (C) 2009 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
> and "show warranty" for details.
> This GDB was configured as "i686-pc-cygwin".
> For bug reporting instructions, please see:
> <http://www.gnu.org/software/gdb/bugs/>...
> Reading symbols from /home/hzhu/gdb/bgdbcygwin/gdb/a.exe...done.
> Setting up the environment for debugging gdb.
> Function "internal_error" not defined.
> Make breakpoint pending on future shared library load? (y or [n])
> [answered N; input not from terminal]
> Function "info_command" not defined.
> Make breakpoint pending on future shared library load? (y or [n])
> [answered N; input not from terminal]
> /home/hzhu/gdb/bgdbcygwin/gdb/.gdbinit:8: Error in sourced command file:
> No breakpoint number 0.
> (gdb) start
> Temporary breakpoint 1 at 0x4010b0: file
> /cygdrive/c/study/gcc/gdb/rec/1.c, line 20.
> Starting program: /home/hzhu/gdb/bgdbcygwin/gdb/a.exe
> [New Thread 3820.0x600]
> [New Thread 3820.0x14c]
> [New Thread 3820.0xf94]
> 
> Temporary breakpoint 1, main () at /cygdrive/c/study/gcc/gdb/rec/1.c:20
> 20             int     b = 0;
> (gdb) gcore
> Can't create a corefile
> (gdb)
> 
>   /* An external target method must build the notes section.  */
>   note_data = target_make_corefile_notes (obfd, &note_size);
> 
> It's target depend.
> 
> It just a error output, better than build error.
> 
> Thanks,
> Hui

Fine, if you can make it work.
I'll be happy to look at a patch.


  parent reply	other threads:[~2009-10-25 18:42 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20091022193607.13598.qmail@sourceware.org>
2009-10-23  7:49 ` Pierre Muller
2009-10-23 15:38   ` Michael Snyder
2009-10-24 22:18     ` Michael Eager
2009-10-24 23:07       ` Michael Snyder
2009-10-25  0:26         ` Hui Zhu
2009-10-25  0:56           ` Hui Zhu
2009-10-25  1:26             ` Michael Snyder
2009-10-25  8:41               ` Hui Zhu
2009-10-25 13:53                 ` Hui Zhu
2009-10-25 18:43                   ` Michael Snyder
2009-10-25 18:42                 ` Michael Snyder [this message]
2009-10-26  2:05                   ` Hui Zhu
2009-10-26  3:41                     ` Michael Snyder
2009-10-26  7:03                       ` Hui Zhu
2009-10-26 15:51                         ` Michael Snyder
2009-10-26 17:20                           ` Pedro Alves
2009-10-26 18:33                             ` Hui Zhu

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=4AE49A75.9030007@vmware.com \
    --to=msnyder@vmware.com \
    --cc=eager@eagercon.com \
    --cc=gdb-patches@sourceware.org \
    --cc=msnyder@sourceware.org \
    --cc=muller@ics.u-strasbg.fr \
    --cc=teawater@gmail.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