public inbox for gdb-cvs@sourceware.org help / color / mirror / Atom feed
From: Simon Marchi <simark@sourceware.org> To: gdb-cvs@sourceware.org Subject: [binutils-gdb] gdb: internal_error -> internal_error_loc in gdb-gdb.gdb.in Date: Tue, 25 Oct 2022 04:13:31 +0000 (GMT) [thread overview] Message-ID: <20221025041331.D3C4A3858D3C@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=a5a0a4fd0ff536a8dbd532864cfc095a306b678c commit a5a0a4fd0ff536a8dbd532864cfc095a306b678c Author: Simon Marchi <simon.marchi@polymtl.ca> Date: Tue Oct 25 00:11:29 2022 -0400 gdb: internal_error -> internal_error_loc in gdb-gdb.gdb.in Commit f34652de0b ("internal_error: remove need to pass __FILE__/__LINE__") renamed the internal_error function to internal_error_loc. Change gdb-gdb.gdb.in accordingly. Change-Id: I876e1623607b6becf74ade53d102ead53a74ed86 Diff: --- gdb/gdb-gdb.gdb.in | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/gdb/gdb-gdb.gdb.in b/gdb/gdb-gdb.gdb.in index 53dca0e08fe..8d97c95a70e 100644 --- a/gdb/gdb-gdb.gdb.in +++ b/gdb/gdb-gdb.gdb.in @@ -5,7 +5,7 @@ if !$gdb_init_done set complaints 1 - b internal_error + b internal_error_loc # This provides an easy way to break into the top-level GDB by # typing "info".
reply other threads:[~2022-10-25 4:13 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20221025041331.D3C4A3858D3C@sourceware.org \ --to=simark@sourceware.org \ --cc=gdb-cvs@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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).