This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
Re: breakpoints/2115: invalid number of printf arguments within command block causes segfault
- From: Daniel Jacobowitz <drow at false dot org>
- To: nobody at sources dot redhat dot com
- Cc: gdb-prs at sources dot redhat dot com,
- Date: 18 Apr 2006 20:18:02 -0000
- Subject: Re: breakpoints/2115: invalid number of printf arguments within command block causes segfault
- Reply-to: Daniel Jacobowitz <drow at false dot org>
The following reply was made to PR breakpoints/2115; it has been noted by GNATS.
From: Daniel Jacobowitz <drow@false.org>
To: unix.gurus@gmail.com
Cc: gdb-gnats@sources.redhat.com
Subject: Re: breakpoints/2115: invalid number of printf arguments within command block causes segfault
Date: Tue, 18 Apr 2006 16:13:20 -0400
On Thu, Apr 13, 2006 at 08:15:33PM -0000, unix.gurus@gmail.com wrote:
> >Synopsis: invalid number of printf arguments within command block causes segfault
> >Release: 6.3
This is a very tricky thing to fix - but fortunately, we've already
fixed it!
There has not yet been a release with the fix, but the next release
will include it. I now get:
Breakpoint 1 at 0x401e40
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912507519568 (LWP 30477)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Switching to Thread 46912507519568 (LWP 30477)]
Breakpoint 1, 0x0000000000401e40 in _init ()
/home/drow/q/test.gdb:5: Error in sourced command file:
Wrong number of arguments for specified format-string
(gdb)
--
Daniel Jacobowitz
CodeSourcery