This is the mail archive of the gdb-prs@sources.redhat.com 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]

gdb/470: add ``maint set moncontrol on/off'' et.al.



>Number:         470
>Category:       gdb
>Synopsis:       add ``maint set moncontrol on/off'' et.al.
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Sat Apr 06 07:28:00 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     ac131313@redhat.com
>Release:        2002-04-05
>Organization:
>Environment:

>Description:
JasonM submitted patches for this long ago.  They unfortunatly went into limbo, several issues were raised: documentation; confusion over when moncontrol() et.al. can be called; handling of -pg.

- A new section (appendix) has since been added, just for commands like this.

- Having grubed around in the profile source code, normal unix-like systems have the moncontrol() and monstartup() functions in both the normal and profiled libc libraries.  Hence, provided the functions are found by configure, they can always be called.

- It is safe (in fact valid) to combine a profiled GDB with non profiled libraries.

Suggest the commands:

  (gdb) maint set moncontrol <enable>
  (gdb) maint set monstartup <lowpc> <highpc>

(I don't remember what the original patch contained.)


>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


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