public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Hui Zhu <teawater@gmail.com>
To: Keith Seitz <keiths@redhat.com>
Cc: insight <insight@sourceware.org>
Subject: Re: [PATCH] Rotate ChangeLog, fix build issues
Date: Sat, 09 Apr 2011 04:14:00 -0000	[thread overview]
Message-ID: <BANLkTikUobS=rEtZtknNeVJVR=NxT2XTDQ@mail.gmail.com> (raw)
In-Reply-To: <4D9F9BB2.1070904@redhat.com>

I am not sure, bug I got:
gcc -g -O2   -I. -I../../src/gdb -I../../src/gdb/common
-I../../src/gdb/config -DLOCALEDIR="\"/usr/local/share/locale\""
-DHAVE_CONFIG_H -I../../src/gdb/../include/opcode
-I../../src/gdb/../opcodes/.. -I../../src/gdb/../readline/.. -I../bfd
-I../../src/gdb/../bfd -I../../src/gdb/../include -I../libdecnumber
-I../../src/gdb/../libdecnumber  -I../../src/gdb/gnulib -Ignulib
-DMI_OUT=1 -DTUI=1  -DGDBTK -I/usr/include/python2.6
-I/usr/include/python2.6 -Wall -Wdeclaration-after-statement
-Wpointer-arith -Wformat-nonliteral -Wno-pointer-sign -Wno-unused
-Wunused-value -Wunused-function -Wno-switch -Wno-char-subscripts
-Werror -c -o gdbtk-bp.o -MT gdbtk-bp.o -MMD -MP -MF
.deps/gdbtk-bp.Tpo -I../../src/gdb/../libgui/src
-I/home/teawater/gdb/cvs/src/tcl/generic
-I/home/teawater/gdb/cvs/src/tk/generic
-DGDBTK_LIBRARY=\"/usr/local/share/insight1.0\"
-DSRC_DIR=\"/home/teawater/gdb/cvs/src/gdb\"
../../src/gdb/gdbtk/generic/gdbtk-bp.c
../../src/gdb/gdbtk/generic/gdbtk-bp.c: In function 'tracepoint_exists':
../../src/gdb/gdbtk/generic/gdbtk-bp.c:834: error: too many arguments
to function 'decode_line_1'
make[2]: *** [gdbtk-bp.o] Error 1
make[2]: Leaving directory `/home/teawater/gdb/cvs/ba/gdb'
make[1]: *** [all-gdb] Error 2
make[1]: Leaving directory `/home/teawater/gdb/cvs/ba'
make: *** [all] Error 2


struct symtabs_and_lines
decode_line_1 (char **argptr, int funfirstline, struct symtab *default_symtab,
	       int default_line, struct linespec_result *canonical)

Thanks,
Hui

On Sat, Apr 9, 2011 at 07:35, Keith Seitz <keiths@redhat.com> wrote:
> Hi,
>
> Now that I have something to commit, it is time to rotate the ChangeLog for
> the year...
>
> I've committed the attached patch, which should fix all the build problems
> that have been reported. Additionally, this should fix a crashing problem
> that I discovered (some time ago) in the register window.
>
> If there are any problems, please let me know.
>
> Keith
>
> ChangeLog
> 2011-04-08  Keith Seitz  <keiths@redhat.com>
>
>        * generic/gdbtk-bp.c (tracepoint_exists): Update for
>        decode_line_1 API change.
>        * generic/gdbtk-cmds.c (gdb_eval): Use comman_val_print
>        instead of val_print.
>        (gdb_get_line_command): Update for decode_line_1 API
>        changes.
>        (gdb_get_file_command): Likewise.
>        (gdb_get_function_command): Likewise.
>        * generic/gdbtk-register.c (get_register_types): Use
>        get_frame_register_value instead of frame_register.
>        (get_register): Pass valid VALUE to val_print.
>        Consolidate calls to get_current_gdbarch.
>        * generic/gdbtk-stack.c (gdb_get_vars_command): Update
>        for decode_line_1 API change.
>

  reply	other threads:[~2011-04-09  4:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-08 23:35 Keith Seitz
2011-04-09  4:14 ` Hui Zhu [this message]
2011-04-09  4:26   ` Keith Seitz
2011-04-12  0:24     ` Kevin Buettner
2011-04-12  5:13       ` Keith Seitz
2011-04-12 15:27         ` 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='BANLkTikUobS=rEtZtknNeVJVR=NxT2XTDQ@mail.gmail.com' \
    --to=teawater@gmail.com \
    --cc=insight@sourceware.org \
    --cc=keiths@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).