Re: Regression (or a new FAIL?): gdb.python/py-events.exp [Re: [PATCH] PR/12691 Add the inferior to Python exited event]

[Kevin Pouget <kevin.pouget@gmail.com>]

On Wed, Oct 5, 2011 at 4:15 PM, Jan Kratochvil
<jan.kratochvil@redhat.com> wrote:
> On Wed, 05 Oct 2011 14:36:36 +0200, Kevin Pouget wrote:
>> How do you test gdbserver? I'm working on a Fedora 15/X86_64, I should
>> be able to reproduce it
>
> There is:
>        http://sourceware.org/gdb/wiki/TestingGDB#Testing_gdbserver_in_a_native_configuration
>
> I use it with my copy:
>        git clone git://vps.jankratochvil.net/nethome
>        mv nethome/src/runtest-gdbserver ~/src/runtest-gdbserver
>        ~/src/runtest-gdbserver/runtest-gdbserver gdb.python/py-events.exp
>
> Reproducible with `CFLAGS=-O0 ./configure ;make' on f15-x86_64.
>
>
> Thanks,
> Jan
>

So I can confirm, it's not a regression but a gdbserver failure:

> $ cat fork.c
> int main (){
>  fork();
> }

> (gdb) target remote :2346
> 0x0000003c47a016b0 in _start () from /lib64/ld-linux-x86-64.so.2
> (gdb) b mainBreakpoint 1 at 0x4004c8: file fork.c, line 2.
> (gdb) cont
> Breakpoint 1, main () at fork.c:22  fork();
> (gdb) set detach-on-fork off
> (gdb) n
> -------------------> Expected: [New process 26420]
> 3 }
> (gdb) quit


what do you want me to do with that, certainly fill a bug report,
shall I change anything in my patch?


Cordially,

Kevin