public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "karl at freefriends dot org" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/12517] New: crash on source of .gdbinit in command file Date: Fri, 25 Feb 2011 01:19:00 -0000 [thread overview] Message-ID: <bug-12517-4717@http.sourceware.org/bugzilla/> (raw) http://sourceware.org/bugzilla/show_bug.cgi?id=12517 Summary: crash on source of .gdbinit in command file Product: gdb Version: 7.2 Status: NEW Severity: normal Priority: P2 Component: gdb AssignedTo: unassigned@sourceware.org ReportedBy: karl@freefriends.org With gdb 7.2, and this file as /home/karl/.gdbinit: define rerun source /home/karl/.gdbinit run end set args a.out I run gdb a.out, where a.out is from hello,world or anything else. At the (gdb) prompt I say "rer" to run the rerun command, and gdb seg fault. Backtrace shows #1 0x080ff7f3 in locate_arg (p=0x19 <Address 0x19 out of bounds>) at ./cli/cli-script.c:730 #2 0x080ff8cb in insert_args (line=0x19 <Address 0x19 out of bounds>) at ./cli/cli-script.c:757 #3 0x080ff085 in execute_control_command (cmd=0x84a6fe8) at ./cli/cli-script.c:411 This is with gdb 7.2 compiled from the original source on ftp.gnu.org, using gcc 4.5.1 also compiled from its original source, on an 32-bit x86 GNU/Linux system (CentOS release 5.4). FWIW, I've had this "define rerun" in my .gdbinit for, oh, 20 years or so and it's been working fine until now :). Thanks, Karl -- Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
next reply other threads:[~2011-02-25 1:19 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-02-25 1:19 karl at freefriends dot org [this message] 2011-04-01 20:54 ` [Bug gdb/12517] " tromey at redhat dot com 2023-12-31 11:29 ` ssbssa at sourceware dot org
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=bug-12517-4717@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@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).