Re: [PATCH] read_file_scope - avoid eventual crash when the file or directory name is null.

[Tom de Vries <tdevries@suse.de>]

On 11/18/25 6:14 PM, Dominic Clifton wrote:
> No, it's not secret.  It's just the blinky example from embassy. Feel free to use it however you like.
> 

I got access today.

I reproduced on x86_64-linux using -readnow:
...
$ gdb -q -batch -readnow blinky
terminate called after throwing an instance of 'std::logic_error'
   what():  basic_string: construction from null is not valid
...

Passes with current trunk.

Bisects to commit 31cb4bb676d ("Correct bounds check when working around 
GAS DWARF 5 directory table bug").

Thanks,
- Tom

> 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
>