Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Salman Khilji" <salmankhilji@hotmail.com>
To: shebs@apple.com
Cc: gdb@sources.redhat.com
Subject: Re: Questions for GDB Developers
Date: Fri, 25 Jan 2002 19:12:00 -0000	[thread overview]
Message-ID: <F1203Vp20N39x6HHGNZ000179c9@hotmail.com> (raw)

I did a little reading on the licensing and yes it does seem that lifting 
the code and creating a proprietory "real-time data monitor" would be 
against the licensing.  However, I do have a few things in my mind and would 
like your opinion on whether it sounds like a good idea:

1)  What I think I could do is lift the symbol handling code and memory 
peeking/poking code and create a "debugger" that does not stop the program 
and allows monitoring of variables in real-time.  The program will only be 
able to read the global variables---no stack variables like a source-line 
debugger.  This part would be released under GPL as open-source.  I will 
implement C and C++.  Others can add whatever they want later on (and of 
course I would like others to help me while I develop this---I don't think I 
can do this on my own!!)

2)  The other GUI parts of the monitoring application including plotting, 
scripting, etc etc would remain proprietory.  Open-source projects like DDD 
could then use the functioality in item 1) to implement real-time monitoring 
features.

This way anyone who wants to create such an application will have the hard 
part already done---that is symbol handling.  This way the core of the 
application will remain open-source and other wil be able to contribute to 
it for future enhancements.

I am sure the real-time community would appreciate this.  So what do you 
think?

Salman


>From: Stan Shebs <shebs@apple.com>
>To: Salman Khilji <salmankhilji@hotmail.com>
>CC: gdb@sources.redhat.com
>Subject: Re: Questions for GDB Developers
>Date: Fri, 25 Jan 2002 14:41:36 -0800
>
>Salman Khilji wrote:
> >
> > 1) Suppose we have to isolate the symbol dictionary code into a separate
> > library so that this library can potentially be used to create a new
> > debugger.   Which source files do we have to include in this library?  I 
>am
> > talking about the code that reads object/symbol files, determines the
> > addresses and types of global variables and dynamically allocated 
>memory.  I
> > am not interested in stack variables.
>
>In general, we haven't been interested in doing this, because the
>usual rationale has been to violate GDB's licensing terms by making
>proprietary debuggers.  If this is for a new free debugger, then it's
>worth talking further.
>
>Stan



_________________________________________________________________
Send and receive Hotmail on your mobile device: http://mobile.msn.com


             reply	other threads:[~2002-01-26  3:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-25 19:12 Salman Khilji [this message]
2002-01-25 19:21 ` Piet/Pete Delaney
  -- strict thread matches above, loose matches on Subject: below --
2002-01-25  4:53 Salman Khilji
2002-01-25 14:41 ` Stan Shebs
2002-01-31 12:34 ` Michael Snyder

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=F1203Vp20N39x6HHGNZ000179c9@hotmail.com \
    --to=salmankhilji@hotmail.com \
    --cc=gdb@sources.redhat.com \
    --cc=shebs@apple.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox