From: Andrew Burgess <aburgess@redhat.com>
To: Roger Sayle <roger@nextmovesoftware.com>, gdb-patches@sourceware.org
Cc: 'Hans-Peter Nilsson' <hp@axis.com>
Subject: Re: [PATCH] Avoid seg fault in sim/cris/sim-if.c
Date: Mon, 03 Aug 2026 13:10:11 +0100 [thread overview]
Message-ID: <877bm7mml8.fsf@redhat.com> (raw)
In-Reply-To: <006501dd21f7$5fa6ab60$1ef40220$@nextmovesoftware.com>
"Roger Sayle" <roger@nextmovesoftware.com> writes:
> Typing "target sim" in GDB built with --target=cris-elf, crashes immediately
> after being launched with "gdb ./a.out". The issue is that STATE_PROG_ARGV
> may return NULL, and this isn't tested before dereferencing the pointer.
>
> If approved, please could someone commit this for me.
> Thanks in advance.
I pushed this.
But also, I owe you an apology. For some reason I was not able to apply
this patch directly from my email client to a git tree as usual, so I
ended up copying the contents by hand. In the process I forgot to make
you the patch author, something I only spotted after pushing to master.
This was not intentional, and I really do apologise, I did not intend to
take credit for this fix. Unfortunately, there's no simple way I can
fix this mistake.
I will try to take greater care in future.
Thanks,
Andrew
>
> 2026-08-01 Roger Sayle <roger@nextmovesoftware.com>
>
> ChangeLog
> * sim/cris/sim-if.c (sim_open): Check that prog_argv isn't NULL.
>
>
> diff --git a/sim/cris/sim-if.c b/sim/cris/sim-if.c
> index 12c80983208..3babbb058b7 100644
> --- a/sim/cris/sim-if.c
> +++ b/sim/cris/sim-if.c
> @@ -770,8 +770,9 @@ sim_open (SIM_OPEN_KIND kind, host_callback *callback, struct bfd *abfd,
> for (envc = 0; environ[envc] != NULL; envc++)
> len += strlen (environ[envc]) + 1;
>
> - for (i = 0; prog_argv[i] != NULL; my_argc++, i++)
> - len += strlen (prog_argv[i]) + 1;
> + if (prog_argv != NULL)
> + for (i = 0; prog_argv[i] != NULL; my_argc++, i++)
> + len += strlen (prog_argv[i]) + 1;
>
> envstart = (envtop - len) & ~8191;
>
next prev parent reply other threads:[~2026-08-03 12:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-01 20:50 Roger Sayle
2026-08-03 12:10 ` Andrew Burgess [this message]
[not found] ` <009501dd2343$a20cc5f0$e62651d0$@nextmovesoftware.com>
2026-08-10 14:07 ` Hans-Peter Nilsson
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=877bm7mml8.fsf@redhat.com \
--to=aburgess@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=hp@axis.com \
--cc=roger@nextmovesoftware.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