This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
RE: Re: [RFC] canonical linespec and multiple breakpoints ...
- From: Avi Gozlan <avi at checkpoint dot com>
- To: Avi Gozlan <avi at checkpoint dot com>, "'Tom Tromey'" <tromey at redhat dot com>, "'gdb-patches at sourceware dot org'" <gdb-patches at sourceware dot org>
- Cc: Matan Ben Gur <matanbg at checkpoint dot com>
- Date: Sun, 25 Sep 2011 13:17:50 +0300
- Subject: RE: Re: [RFC] canonical linespec and multiple breakpoints ...
- References: <9C4E85B61203CD419BB3A638E5F6833301E5CA98B64F@il-ex01.ad.checkpoint.com>
Any reference to the below issues would be appreciated. Thanks.
-----Original Message-----
From: Avi Gozlan
Sent: Sunday, September 18, 2011 1:22 PM
To: 'Tom Tromey'; 'gdb-patches@sourceware.org'
Cc: Avi Gozlan; Matan Ben Gur
Subject: Re: [RFC] canonical linespec and multiple breakpoints ...
Hello,
On the basis of your proposal dealing with supporting multiple breakpoints
and the discussion that followed it, I would like to raise some questions.
These issues are highly relevant for our needs (the need was first described
in bug 12313 in the GDB bug database).
Among varying GDB uses, we use GDB to debug a process which loads (using
dlopen) the same exact library multiple times (in fact there are copies of
the library otherwise dlopen returns the same handle for each load). We find
your proposal very useful for us to be able to attach to the process and
debug a specific library. Though, we do have some questions and suggestions.
Pardon technical inaccuracies in GDB terminology.
1) The proposal discusses function breakpoints. Will it also enable
inspecting global and static variables from a specific library?
2) Just to make sure we understand the interaction of the user interface
with "set multiple-symbols": it will be possible to request GDB for a
specific variable/function by a library name without getting it from all
libraries or get a question (ask) each time, right? Otherwise it will be
very inconvenient to inspect multiple variables within a given library.
3) Will the library specific interface know how to handle non-stripped
libraries that are compiled without debug information (no "-g")?
4) We suggest adding an option to enable the GDB backtrace command to
show the library name for each function. In our usage case we have
scenarios in which the libraries interact with each other and a backtrace
showing the library name for each function can enable us understand the
interaction perfectly.
5) Perhaps a little pedantic but what about handling symbols with
different names in libraries with identical name which lie in different
paths?
Thanks,
Avi