time to create the gdb-7.0.1 release (?)

Hui Zhu teawater@gmail.com
Fri Dec 18 09:02:00 GMT 2009


OK.  Never mind.

(gdb) c
Continuing.
a = 0 b = 0 c = 1
a = 3
a = 3 b = 3 c = 1
a = 3 b = 3 c = 2
a = 1 b = 3 c = 2
The next instruction is syscall exit_group.  It will make the program
exit.  Do you want to stop the program?([y] or n)
Process record: inferior program stopped.

Program received signal SIGTRAP, Trace/breakpoint trap.
0xb7fe3405 in __kernel_vsyscall ()
(gdb) c
Continuing.
The next instruction is syscall exit_group.  It will make the program
exit.  Do you want to stop the program?([y] or n)
Process record: inferior program stopped.

Program received signal SIGABRT, Aborted.
0xb7fe3405 in __kernel_vsyscall ()
(gdb) c
Continuing.

Program terminated with signal SIGABRT, Aborted.
The program no longer exists.


This bug will keep affect 7.0.1.  :(

Hui


On Fri, Dec 18, 2009 at 16:55, Joel Brobecker <brobecker@adacore.com> wrote:
>> http://sourceware.org/ml/gdb-patches/2009-12/msg00010.html
>
> I didn't think that this patch was proposed for 7.0.1?
>
> --
> Joel
>



More information about the Gdb mailing list