This is the mail archive of the gdb-patches@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]

Re: patch to add QNX NTO i386 support



   The only way to tell that we're targetting a qnx binary will be when
   someone types 'target qnx ...'.  Is it acceptable to have the
   gdbarch stuff come into play when someone does that targetting?

I'm not sure.  If the "qnx" protocol implies that the OS/ABI is QNX,
this would make sense to me, but there are other people on this list
that could judge better.

You're right about this.  It's unlikely that anyone else would use our qnx
pdebug protocol for remote debugging but one of my future projects is to
port the gdbserver to Neutrino.  People wouldn't necessarily need to use
pdebug but in this case, there would really be no way of knowing the ABI
other than having a default set.
FYI,

A long term objective of GDB is to get the sequence:

$ gdb
(gdb) target remote who-knows-what-we-debugging:47
Connected to target who-knows-what-we-debugging.
Architecture set to now-we-know.
(gdb) info registers
... display of now-we-know architecture's registers ...
(gdb)

This involves the target supplying the thread's architecture via the target stack ....

Andrew



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