debugging tools policy

QNX Newsgroups (Archives) qdn.public.qnxrtp.advocacy
1

Hi,

Could you please explain us what will happen with the debugging tools.

I heard talking that pdb is gone.

I heard talking that your are writting a new debugger.

I don’t really understand, ok to forget pdb, ddd is a good product.

The problemm with ddd is that xphoton doesn’t support localization.

Why writting a new debugger?

Why xphoton is not a priority?

working on xphoton will give us the possibility to use a powerfull tool
(ddd) and also the possibility to use lot of very interesting
applications.

Isn’t it better?

Thanks,
Alain.

2

Alain Bonnefoy wrote:

Hi,

Could you please explain us what will happen with the debugging tools.

I heard talking that pdb is gone.

I heard talking that your are writting a new debugger.

I don’t really understand, ok to forget pdb, ddd is a good product.

The problemm with ddd is that xphoton doesn’t support localization.

Why writting a new debugger?

Why xphoton is not a priority?

working on xphoton will give us the possibility to use a powerfull tool
(ddd) and also the possibility to use lot of very interesting
applications.

Isn’t it better?

‘The popular command-line GNU development tools’ are still there …
are you not satisfied with them??

From http://www.qnx.com/news/openplatform_data.html … the best
satires are made by the reality:

QNX is … developer friendly
[ clip …]
the best tools
[ clip …]
The popular command-line GNU development tools are included with the
platform, as are graphical debuggers and third-party development
tools. And, of course, since QNX Neutrino and Linux share the same
POSIX APIs, almost any Linux development tool can be easily ported
to and used with QNX.

Armin




Thanks,
Alain.

3

Alain Bonnefoy wrote:

Hi,

Could you please explain us what will happen with the debugging tools.

I heard talking that pdb is gone.

I heard talking that your are writting a new debugger.

I don’t really understand, ok to forget pdb, ddd is a good product.

Alain,

you are right, DDD is a good product, even a ‘GPL product’!!

QSSL is not willing to open up their modified GPL DDD sources …
they are claiming that they haven’t made any changes with DDD.
But after trying to port DDD it is evident that there have been
changes neccessary. That means nobody is able to fix problems of
their DDD port … for my understanding it’s a misinterpretion of
GPL licenses!

Armin



The problemm with ddd is that xphoton doesn’t support localization.

Why writting a new debugger?

Why xphoton is not a priority?

working on xphoton will give us the possibility to use a powerfull tool
(ddd) and also the possibility to use lot of very interesting
applications.

Isn’t it better?

Thanks,
Alain.

4

Armin Steinhoff <A-Steinhoff@web_.de> wrote:

…
Alain,

you are right, DDD is a good product, even a ‘GPL product’!!

QSSL is not willing to open up their modified GPL DDD sources …
they are claiming that they haven’t made any changes with DDD.
But after trying to port DDD it is evident that there have been
changes neccessary. That means nobody is able to fix problems of
their DDD port … for my understanding it’s a misinterpretion of
GPL licenses!

Armin -

I will look into the issue of the DDD source for you, please feel free
to followup with me by email.

  • Eric
    –
    Eric Johnson
    QA Mgr, QNX Software Systems Ltd.
5

Eric Johnson <eric@qnx.com> wrote:

Armin Steinhoff <A-Steinhoff@web_.de> wrote:
…
Alain,

you are right, DDD is a good product, even a ‘GPL product’!!

QSSL is not willing to open up their modified GPL DDD sources …
they are claiming that they haven’t made any changes with DDD.
But after trying to port DDD it is evident that there have been
changes neccessary. That means nobody is able to fix problems of
their DDD port … for my understanding it’s a misinterpretion of
GPL licenses!

Ok. Once again, let me say that we did not change any source in DDD.
Once again, let me say that we did not change any source in DDD.
Once again, let me say that we did not change any source in DDD.
Once again, let me say that we did not change any source in DDD.
…


All modifications have to do with the config. Just part of the joy of
porting. :slight_smile:


Please do the following.

Building DDD

  • Go to gnu and download DDD-3.2.1

  • Get Motif (try http://www.openmotif.com/)

  • un-tar the GNU archive.

  • Replace all copies of config.sub and config.guess with correct ones.
    (See config.guess and config.sub in any of the gnu sources we have
    posted at http://staff.qnx.com/~cburgess/gnu/).

  • Run configure with the --disable-builtin-app-defaults,
    –with-motif-libraries and
    –with-motif-includes options…

  • Change ddd/config.h HAVE_XMUSEVERSION to be 0 instead of 1

  • Change all the Makefiles

  • Change -O to -O1

  • Remove -g entirely.

  • Change ddd/Makefile as follows
    locate the target install and remove the dependency on install-info
    and add the following 2 lines
    cp …/XErrorDB $(prefix)
    cp …/XKeysymDB $(prefix)

NOTE (options.C) in the ddd directory will not compile with both -Ox and -g.
It generates an internal compiler error.

  • type make and wait for it to complete

  • cd ddd from the top of the build tree and modify USERINFO to contain
    a vaild qnx.com Email address. We have used “support@qnx.com”

  • type make

  • cd …

  • make install

Running DDD

  • Copy XErrorDB and XKeysymDB into /user/X11R6/lib/X11
  • set the following environment variables
    export XErrorDB=/usr/X11R6/lib/X11/XErrorDB
    export XKeysymDB=/usr/X11R6/lib/X11/XKeysymDB


    Regards,
    GP

Armin -

I will look into the issue of the DDD source for you, please feel free
to followup with me by email.

  • Eric
    –
    Eric Johnson
    QA Mgr, QNX Software Systems Ltd.

–

Graeme Peterson
QNX Tools Group
gp@qnx.com

6

I did the same thing long before DDD was available from QNX, so I can
confirm it works, Armin :wink:

  • igor

Graeme Peterson wrote:

Eric Johnson <> eric@qnx.com> > wrote:
Armin Steinhoff <A-Steinhoff@web_.de> wrote:
…
Alain,

you are right, DDD is a good product, even a ‘GPL product’!!

QSSL is not willing to open up their modified GPL DDD sources …
they are claiming that they haven’t made any changes with DDD.
But after trying to port DDD it is evident that there have been
changes neccessary. That means nobody is able to fix problems of
their DDD port … for my understanding it’s a misinterpretion of
GPL licenses!

Ok. Once again, let me say that we did not change any source in DDD.
Once again, let me say that we did not change any source in DDD.
Once again, let me say that we did not change any source in DDD.
Once again, let me say that we did not change any source in DDD.
…

All modifications have to do with the config. Just part of the joy of
porting. > :slight_smile:

Please do the following.

Building DDD

  • Go to gnu and download DDD-3.2.1

  • Get Motif (try > http://www.openmotif.com/> )

  • un-tar the GNU archive.

  • Replace all copies of config.sub and config.guess with correct ones.
    (See config.guess and config.sub in any of the gnu sources we have
    posted at > http://staff.qnx.com/~cburgess/gnu/> ).

  • Run configure with the --disable-builtin-app-defaults,
    –with-motif-libraries and
    –with-motif-includes options…

  • Change ddd/config.h HAVE_XMUSEVERSION to be 0 instead of 1

  • Change all the Makefiles

  • Change -O to -O1

  • Remove -g entirely.

  • Change ddd/Makefile as follows
    locate the target install and remove the dependency on install-info
    and add the following 2 lines
    cp …/XErrorDB $(prefix)
    cp …/XKeysymDB $(prefix)

NOTE (options.C) in the ddd directory will not compile with both -Ox and -g.
It generates an internal compiler error.

  • type make and wait for it to complete

  • cd ddd from the top of the build tree and modify USERINFO to contain
    a vaild qnx.com Email address. We have used "> support@qnx.com> "

  • type make

  • cd …

  • make install

Running DDD

  • Copy XErrorDB and XKeysymDB into /user/X11R6/lib/X11
  • set the following environment variables
    export XErrorDB=/usr/X11R6/lib/X11/XErrorDB
    export XKeysymDB=/usr/X11R6/lib/X11/XKeysymDB

Regards,
GP

Armin -

I will look into the issue of the DDD source for you, please feel free
to followup with me by email.

  • Eric
    –
    Eric Johnson
    QA Mgr, QNX Software Systems Ltd.

–

Graeme Peterson
QNX Tools Group
gp@qnx.com

7

“Graeme Peterson” <gp@qnx.com> wrote in message
news:9764o2$42u$1@nntp.qnx.com…

Building DDD

There’s a little trouble here. I don’t believe QNX fits definition of open
source OS according to OpenMotif license. Running OpenMotif on QNX would be
violation of license then. Not to mention that building OpenMotif is
separate story deserving its own chapter :wink:

One could go with Lesstif of course. It works too and builds easier.

  • igor
8

Alain Bonnefoy a écrit :

Hi,

Could you please explain us what will happen with the debugging tools.

I heard talking that pdb is gone.

I heard talking that your are writting a new debugger.

I don’t really understand, ok to forget pdb, ddd is a good product.

The problemm with ddd is that xphoton doesn’t support localization.

Why writting a new debugger?

Why xphoton is not a priority?

working on xphoton will give us the possibility to use a powerfull tool
(ddd) and also the possibility to use lot of very interesting
applications.

Isn’t it better?

Thanks,
Alain.

… what about the subject of my question ?

Thanks,
Alain.

9

Alain Bonnefoy <alain.bonnefoy@icbt.com> wrote:

Alain Bonnefoy a ecrit :

Hi,

Could you please explain us what will happen with the debugging tools.

I heard talking that pdb is gone.

I heard talking that your are writting a new debugger.

I don’t really understand, ok to forget pdb, ddd is a good product.

The problemm with ddd is that xphoton doesn’t support localization.

Why writting a new debugger?

Why xphoton is not a priority?

working on xphoton will give us the possibility to use a powerfull tool
(ddd) and also the possibility to use lot of very interesting
applications.

Isn’t it better?

Thanks,
Alain.

… what about the subject of my question ?

Thanks,
Alain.

I cannot speak to our corporate policy, or xphoton and internationalization.
However, pdb is gone. I no longer see it in the latest upgrade.

We should differentiate between the debugger and the GUI stuck on top
of it. We are sticking with GDB, however we are moving to GDB-5.0 across
the board. So from that perspective, we are not re-writing the debugger.

Most of the GUI front ends to GDB run separate from GDB, and wind up parsing
gdb’s stdio. So gdb thinks it is getting text input from a console, and
the GUI translates the output and presents it in a nice graphical format.

(From Andrew Cagney’s libGDB article posted at
http://sources.redhat.com/gdb/papers/libgdb2/):

" Unfortunately this technique has several limitations:

  • it is very sensitive to changes in GDB’s output
  • performance is restricted by the speed of communication between the
    GUI and GDB
  • it was difficult to keep the GUI consistent with the CLI "

There is an initiative to make gdb a library. This is (I think) the second
attempt at this, the first was called ‘libgdb’ and the second is called
‘libGDB’ or ‘libgdb2’. Please see the above URL and article for a more
complete discussion of these issues. These are some of the issues we are
evaluating as far as our debuggers go.

You may need to post your xphoton/internationalization question in a
different qdn news group, perhaps: qdn.public.qnxrtp.applications.

Regards,
GP

Graeme Peterson
QNX Tools Group
gp@qnx.com

10

I haven’t tried in earlier versions, but rtp 6.1 definitely
won’t work. see my post in qdn.public.qnxrtp.devtools: c++ bad on rtp 6.1?

Frank

Igor Kovalenko <Igor.Kovalenko@motorola.com> wrote:

I did the same thing long before DDD was available from QNX, so I can
confirm it works, Armin > :wink:

  • igor

Graeme Peterson wrote:

Eric Johnson <> eric@qnx.com> > wrote:
Armin Steinhoff <A-Steinhoff@web_.de> wrote:
…
Alain,

you are right, DDD is a good product, even a ‘GPL product’!!

QSSL is not willing to open up their modified GPL DDD sources …
they are claiming that they haven’t made any changes with DDD.
But after trying to port DDD it is evident that there have been
changes neccessary. That means nobody is able to fix problems of
their DDD port … for my understanding it’s a misinterpretion of
GPL licenses!

Ok. Once again, let me say that we did not change any source in DDD.
Once again, let me say that we did not change any source in DDD.
Once again, let me say that we did not change any source in DDD.
Once again, let me say that we did not change any source in DDD.
…

All modifications have to do with the config. Just part of the joy of
porting. > :slight_smile:

Please do the following.

Building DDD

  • Go to gnu and download DDD-3.2.1

  • Get Motif (try > http://www.openmotif.com/> )

  • un-tar the GNU archive.

  • Replace all copies of config.sub and config.guess with correct ones.
    (See config.guess and config.sub in any of the gnu sources we have
    posted at > http://staff.qnx.com/~cburgess/gnu/> ).

  • Run configure with the --disable-builtin-app-defaults,
    –with-motif-libraries and
    –with-motif-includes options…

  • Change ddd/config.h HAVE_XMUSEVERSION to be 0 instead of 1

  • Change all the Makefiles

  • Change -O to -O1

  • Remove -g entirely.

  • Change ddd/Makefile as follows
    locate the target install and remove the dependency on install-info
    and add the following 2 lines
    cp …/XErrorDB $(prefix)
    cp …/XKeysymDB $(prefix)

NOTE (options.C) in the ddd directory will not compile with both -Ox and -g.
It generates an internal compiler error.

  • type make and wait for it to complete

  • cd ddd from the top of the build tree and modify USERINFO to contain
    a vaild qnx.com Email address. We have used "> support@qnx.com> "

  • type make

  • cd …

  • make install

Running DDD

  • Copy XErrorDB and XKeysymDB into /user/X11R6/lib/X11
  • set the following environment variables
    export XErrorDB=/usr/X11R6/lib/X11/XErrorDB
    export XKeysymDB=/usr/X11R6/lib/X11/XKeysymDB

Regards,
GP

Armin -

I will look into the issue of the DDD source for you, please feel free
to followup with me by email.

  • Eric
    –
    Eric Johnson
    QA Mgr, QNX Software Systems Ltd.

–

Graeme Peterson
QNX Tools Group
gp@qnx.com

11

Thanks for your post GP!
I finally have a chance to try ddd port. It looks like it is not
as easy as you thought! Maybe because of the bad c++ in rtp 6.1.
See my post in qdn.public.qnxrtp.devtools “c++ bad on rtp 6.1?”.
I’d love to hear your thought.
Frank

Graeme Peterson <gp@qnx.com> wrote:

Eric Johnson <> eric@qnx.com> > wrote:
Armin Steinhoff <A-Steinhoff@web_.de> wrote:
…
Alain,

you are right, DDD is a good product, even a ‘GPL product’!!

QSSL is not willing to open up their modified GPL DDD sources …
they are claiming that they haven’t made any changes with DDD.
But after trying to port DDD it is evident that there have been
changes neccessary. That means nobody is able to fix problems of
their DDD port … for my understanding it’s a misinterpretion of
GPL licenses!

Ok. Once again, let me say that we did not change any source in DDD.
Once again, let me say that we did not change any source in DDD.
Once again, let me say that we did not change any source in DDD.
Once again, let me say that we did not change any source in DDD.
…



All modifications have to do with the config. Just part of the joy of
porting. > :slight_smile:



Please do the following.

Building DDD

  • Go to gnu and download DDD-3.2.1

  • Get Motif (try > http://www.openmotif.com/> )

  • un-tar the GNU archive.

  • Replace all copies of config.sub and config.guess with correct ones.
    (See config.guess and config.sub in any of the gnu sources we have
    posted at > http://staff.qnx.com/~cburgess/gnu/> ).

  • Run configure with the --disable-builtin-app-defaults,
    –with-motif-libraries and
    –with-motif-includes options…

  • Change ddd/config.h HAVE_XMUSEVERSION to be 0 instead of 1

  • Change all the Makefiles

  • Change -O to -O1

  • Remove -g entirely.

  • Change ddd/Makefile as follows
    locate the target install and remove the dependency on install-info
    and add the following 2 lines
    cp …/XErrorDB $(prefix)
    cp …/XKeysymDB $(prefix)

NOTE (options.C) in the ddd directory will not compile with both -Ox and -g.
It generates an internal compiler error.

  • type make and wait for it to complete

  • cd ddd from the top of the build tree and modify USERINFO to contain
    a vaild qnx.com Email address. We have used "> support@qnx.com> "

  • type make

  • cd …

  • make install

Running DDD

  • Copy XErrorDB and XKeysymDB into /user/X11R6/lib/X11
  • set the following environment variables
    export XErrorDB=/usr/X11R6/lib/X11/XErrorDB
    export XKeysymDB=/usr/X11R6/lib/X11/XKeysymDB



    Regards,
    GP

Armin -

I will look into the issue of the DDD source for you, please feel free
to followup with me by email.

  • Eric
    –
    Eric Johnson
    QA Mgr, QNX Software Systems Ltd.

–

Graeme Peterson
QNX Tools Group
gp@qnx.com