This is the mail archive of the mailing list for the GDB project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: [PATCH] btrace: initiate teardown when closing record btrace target

> -----Original Message-----
> From: [mailto:gdb-patches-
>] On Behalf Of Jan Kratochvil
> Sent: Tuesday, January 21, 2014 3:17 PM

> On Mon, 20 Jan 2014 10:00:21 +0100, Markus Metzger wrote:
> > In the remote case, the remote target that provides to_teardown_btrace
> > to free the GDB side resources has already been unpushed when threads
> > are destroyed.  This results in a complaint "You can't do this ..." and
> > in a few bytes of memory leaked for each thread.
> Could you provide an example when this error happens?
> I can reproduce it with plain gdb+gdbserver but not with btrace functionality.

It happens with a simple hello-world.

$ gdbserver :2001 hello
$ gdb hello
(gdb) target remote :2001
(gdb) rec b
(gdb) kill
Kill the program being debugged? (y or n) y
You can't do that when your target is 'exec'.

When I set a breakpoint at tcomplain and go up, I'm in taret_teardown_btrace.


Intel GmbH
Dornacher Strasse 1
85622 Feldkirchen/Muenchen, Deutschland
Sitz der Gesellschaft: Feldkirchen bei Muenchen
Geschaeftsfuehrer: Christian Lamprechter, Hannes Schwaderer, Douglas Lusk
Registergericht: Muenchen HRB 47456
Ust.-IdNr./VAT Registration No.: DE129385895
Citibank Frankfurt a.M. (BLZ 502 109 00) 600119052

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]