Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Dominic Clifton" <me@dominicclifton.name>
To: "'Tom de Vries'" <tdevries@suse.de>,
	"'Andrew Burgess'" <aburgess@redhat.com>,
	<gdb-patches@sourceware.org>
Subject: RE: [PATCH] read_file_scope - avoid eventual crash when the file or directory name is null.
Date: Tue, 18 Nov 2025 18:14:16 +0100	[thread overview]
Message-ID: <03a001dc58ae$c54f88f0$4fee9ad0$@dominicclifton.name> (raw)
In-Reply-To: <070f3bc9-3080-4bf7-b31b-96edc04997b3@suse.de>

No, it's not secret.  It's just the blinky example from embassy. Feel free to use it however you like.

Thanks,

Dominic

-----Original Message-----
From: Tom de Vries <tdevries@suse.de> 
Sent: 18 November 2025 09:39
To: Dominic Clifton <me@dominicclifton.name>; 'Andrew Burgess' <aburgess@redhat.com>; gdb-patches@sourceware.org
Subject: Re: [PATCH] read_file_scope - avoid eventual crash when the file or directory name is null.

On 10/16/25 12:53 AM, Dominic Clifton wrote:
> The elf file in question is here:
> 
> https://drive.google.com/file/d/1um3lJFHTvLHdAZdM7D-hLMmdsGJneDeC/view
> ?usp=s
> haring

I've clicked on this link, had to login to a google account and request access.

Is the binary "secret" in some way, or could I attach it in some bug report (assuming it's small enough)?

Thanks,
- Tom


  reply	other threads:[~2025-11-18 17:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-05 15:03 Fixing gdb crash issue when loading an elf file compiled with rust 1.87.0 Dominic Clifton
2025-10-09 17:35 ` [PATCH] read_file_scope - avoid eventual crash when the file or directory name is null Dominic Clifton
2025-10-13 17:14   ` Andrew Burgess
2025-10-15 22:53     ` Dominic Clifton
2025-11-18  8:38       ` Tom de Vries
2025-11-18 17:14         ` Dominic Clifton [this message]
2025-11-27 15:02           ` Tom de Vries
2025-11-27 23:22             ` Dominic Clifton
2025-10-09 17:37 ` Fixing gdb crash issue when loading an elf file compiled with rust 1.87.0 Dominic Clifton

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='03a001dc58ae$c54f88f0$4fee9ad0$@dominicclifton.name' \
    --to=me@dominicclifton.name \
    --cc=aburgess@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tdevries@suse.de \
    /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