From: Pedro Alves <pedro@palves.net>
To: Luis Machado <lgustavo@codesourcery.com>, gdb-patches@sourceware.org
Cc: sandra@codesourcery.com
Subject: Re: [PATCH, v4] PR 20569, segv in follow_exec
Date: Tue, 25 Oct 2016 19:46:00 -0000 [thread overview]
Message-ID: <5b758a61-90ec-19c3-d2db-7d88aec272f5@palves.net> (raw)
In-Reply-To: <87c593b9-b811-d104-65fc-4225d46d5581@codesourcery.com>
On 10/25/2016 08:41 PM, Luis Machado wrote:
> Going back to the flags problem, maybe adding "add_flags" as argument to
> symbol_file_add_main_1, just like symbol_file_add, and appending those
> flags to the existing flag variable there would make things work?
I've now cleaned up that patch, and simply rebasing yours on top
shows what I meant:
src/gdb/exec.c:184:59: error: could not convert ‘flags’ from
‘symfile_add_flags {aka enum_flags<symfile_add_flag>}’ to
‘objfile_flags {aka enum_flags<objfile_flag>}’
symbol_file_add_main_1 (exec_file_host, from_tty, flags);
^
Makefile:1138: recipe for target 'exec.o' failed
I.e., the existing flags parameter to symbol_file_add_main_1
is _not_ a symfile_add_flags. We can't just use it as is.
So yes, I think so. I was just doing that here, this minute.
But I was replacing the from_tty parameter symbol_file_add_main
with a symfile_add_flags instead. Let me do that and send
both patches.
next prev parent reply other threads:[~2016-10-25 19:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-25 17:12 Luis Machado
2016-10-25 18:04 ` Pedro Alves
2016-10-25 18:16 ` Luis Machado
2016-10-25 18:20 ` Pedro Alves
2016-10-25 18:31 ` Luis Machado
2016-10-25 19:41 ` Luis Machado
2016-10-25 19:46 ` Pedro Alves [this message]
2016-10-25 19:50 ` Luis Machado
2016-10-25 23:40 ` [PATCH v5 2/2] " Pedro Alves
2016-10-26 14:28 ` Luis Machado
2016-10-26 16:05 ` Luis Machado
2016-10-27 14:09 ` Pedro Alves
2016-10-25 23:40 ` [PATCH v5 1/2] Make symfile_add_flags and objfile->flags strongly typed Pedro Alves
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=5b758a61-90ec-19c3-d2db-7d88aec272f5@palves.net \
--to=pedro@palves.net \
--cc=gdb-patches@sourceware.org \
--cc=lgustavo@codesourcery.com \
--cc=sandra@codesourcery.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