Page MenuHome GnuPG
Create Task
Maniphest T4932

gpgmepp segfaults during keys listing on Windows
Open, LowPublic
Actions

Description

Attached program segfaults on Windows when listing keys, precisely on

const auto key = ctx->nextKey(error);

It does so if GPGME_DEBUG is not present or GPGME_DEBUG <=6.
It doesn't segfault if GPGME_DEBUG > 6. Then it shows my single key in keyring.

Additional info:

  1. Gpg4win 3.1.11 installed in C:\Program Files (x86)
  2. self-compiled Libassuan 2.5.3
  3. self-compiled Libgpg-error 1.37
  4. self-compiled GPGME 1.13.1
  5. no extra patches used
  6. CFLAGS and CXXFLAGS are equal to "-Og -g"
  7. Windows 7, 64 bit, Polish locale
  8. g++.exe (Rev2, Built by MSYS2 project) 9.3.0
  9. used msys2-x86_64-20190524.exe with mingw64 installed

gpgcrash.zip5 KBDownload

Details

Version
1.13.1

Event Timeline

wojnilowicz created this task.May 1 2020, 8:34 PM
wojnilowicz created this object in space S1 Public.

Attaching the actual program

gpgcrash.zip5 KBDownload

• aheinecke triaged this task as Low priority.May 8 2020, 11:24 AM
• aheinecke added a subscriber: • aheinecke.

If you have -g / -Og could you please provide a backtrace?

We are not really supporting MSVC builds, so I'm triaging this with Low prio, but we would help analyzing the issue. I won't go so far as to debug your binaries myself.

wojnilowicz added a comment.May 8 2020, 2:01 PM
In T4932#134540, @aheinecke wrote:

If you have -g / -Og could you please provide a backtrace?

It's in the attached file already. Have you looked at it?

We are not really supporting MSVC builds, so I'm triaging this with Low prio, but we would help analyzing the issue.

It's not MSVC build. It's MinGW build in MSYS2 environment.

I won't go so far as to debug your binaries myself.

You could build your own binary yourself. I've attached a minimal test case.