Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: Christian Biesinger <cbiesinger@google.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 7/7] Add handling for 64-bit module addresses in Cygwin core dumps
Date: Wed, 8 Jul 2020 16:50:41 +0100	[thread overview]
Message-ID: <d9161f81-7cd4-7cdc-07c3-fc28daad9337@dronecode.org.uk> (raw)
In-Reply-To: <CAPTJ0XHvPgUTfUByjWi93u_Bx8TmgOQAmi1RxsJApNsVV5R-xA@mail.gmail.com>

On 06/07/2020 21:13, Christian Biesinger via Gdb-patches wrote:
> On Wed, Jul 1, 2020 at 4:34 PM Jon Turney <jon.turney@dronecode.org.uk> wrote:
>> --- a/bfd/elf.c
>> +++ b/bfd/elf.c
>> @@ -10185,10 +10185,19 @@ elfcore_grok_win32pstatus (bfd *abfd, Elf_Internal_Note *note)
>>         break;
>>
>>       case 3 /* NOTE_INFO_MODULE */:
>> -      /* Make a ".module/xxxxxxxx" section.  */
>> +    case 4 /* NOTE_INFO_MODULE64 */:
> 
> It really seems like these should be actual constants, which would
> also make it easier to understand...

Absolutely.

Before [1], this structure was defined by including Cygwin's 
<sys/procfs.h> (so this code didn't work in cross-environments).

I can't find a model of adding note structure definitions (the other 
grok_note functions seem to rely on OS definitions), so I'm not sure 
what kind of change you are asking me to make in this patch.

[1] 
https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=4a6636fbb5c051fbe15d18a005a2a505ef652571

> 
>> +      /* Make a ".module/<base_address>" section.  */
>>         /* module_info.base_address */
>> -      base_addr = bfd_get_32 (abfd, note->descdata + 4);
>> -      sprintf (buf, ".module/%08lx", (unsigned long) base_addr);
>> +      if (type == 3)
> 
> ...this if.
> 
>> --- a/gdb/windows-tdep.c
>> +++ b/gdb/windows-tdep.c
>> +  if (data_type == 3) /* NOTE_INFO_MODULE */
> 
> Same here.


  reply	other threads:[~2020-07-08 15:50 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-01 21:32 [PATCH 0/7] Add gdb support for Cygwin x86_64 " Jon Turney
2020-07-01 21:32 ` [PATCH 1/7] Read tid from correct offset in win32pstatus NOTE_INFO_THREAD Jon Turney
2020-07-01 21:32 ` [PATCH 2/7] Don't apply size constraint to all win32pstatus ELF notes Jon Turney
2020-07-01 21:32 ` [PATCH 3/7] Don't hardcode CONTEXT size for a NOTE_INFO_THREAD win32pstatus note Jon Turney
2020-07-06 20:12   ` Christian Biesinger
2020-07-01 21:32 ` [PATCH 4/7] Add sniffer for Cygwin x86_64 core dumps Jon Turney
2020-07-02 23:59   ` Simon Marchi
2020-07-03 13:30     ` Jon Turney
2020-07-03 14:17       ` Simon Marchi
2020-07-06 18:46         ` Jon Turney
2020-07-01 21:32 ` [PATCH 5/7] Add amd64_windows_gregset_reg_offset Jon Turney
2020-07-03 14:11   ` Pedro Alves
2020-07-01 21:32 ` [PATCH 6/7] Promote windows_core_xfer_shared_libraries and windows_core_pid_to_str Jon Turney
2020-07-02 23:53   ` Simon Marchi
2020-07-02 23:56     ` Simon Marchi
2020-07-03 13:14       ` Jon Turney
2020-07-01 21:32 ` [PATCH 7/7] Add handling for 64-bit module addresses in Cygwin core dumps Jon Turney
2020-07-06 20:13   ` Christian Biesinger
2020-07-08 15:50     ` Jon Turney [this message]
2020-07-08 16:11       ` Christian Biesinger
2020-07-12 12:58         ` Jon Turney
2020-07-02 21:17 ` [PATCH 0/7] Add gdb support for Cygwin x86_64 " Tom Tromey
2020-07-03 13:30   ` Jon Turney
2020-07-03  0:00 ` Simon Marchi

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=d9161f81-7cd4-7cdc-07c3-fc28daad9337@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=cbiesinger@google.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