Discussions
Categories
- 385.5K All Categories
- 5.1K Data
- 2.5K Big Data Appliance
- 2.5K Data Science
- 453.4K Databases
- 223.2K General Database Discussions
- 3.8K Java and JavaScript in the Database
- 47 Multilingual Engine
- 606 MySQL Community Space
- 486 NoSQL Database
- 7.9K Oracle Database Express Edition (XE)
- 3.2K ORDS, SODA & JSON in the Database
- 585 SQLcl
- 4K SQL Developer Data Modeler
- 188K SQL & PL/SQL
- 21.5K SQL Developer
- 46 Data Integration
- 46 GoldenGate
- 298.4K Development
- 4 Application Development
- 20 Developer Projects
- 166 Programming Languages
- 295K Development Tools
- 150 DevOps
- 3.1K QA/Testing
- 646.7K Java
- 37 Java Learning Subscription
- 37.1K Database Connectivity
- 201 Java Community Process
- 108 Java 25
- 22.2K Java APIs
- 138.3K Java Development Tools
- 165.4K Java EE (Java Enterprise Edition)
- 22 Java Essentials
- 176 Java 8 Questions
- 86K Java Programming
- 82 Java Puzzle Ball
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 94.3K Java SE
- 13.8K Java Security
- 208 Java User Groups
- 25 JavaScript - Nashorn
- Programs
- 667 LiveLabs
- 41 Workshops
- 10.3K Software
- 6.7K Berkeley DB Family
- 3.6K JHeadstart
- 6K Other Languages
- 2.3K Chinese
- 207 Deutsche Oracle Community
- 1.1K Español
- 1.9K Japanese
- 474 Portuguese
dbxtool uses 32 bit version of dbx instead of 64 bit version (linux)

When I start dbxtool from the command line via dbxtool "my_prog my_args", the GUI launches and a popup appears saying
dbx: 32-bit dbx can't debug 64-bit app
I installed developer studio 12.6 from the tar.bz2 file on Linux RHEL7 and added
OracleDeveloperStudio12.6-linux-x86-bin/developerstudio12.6/bin
to my path.
Note that dbx -c "runargs my_args" my_prog starts just fine.
I read that the workaround was to stop the originally launched dbx and reload the program which does indeed work but that is rather inconvenient and I would really like to get this working out of the box. Can someone help me on this? (Editing the startup scripts etc. would not be a problem for me)
Answers
-
Correction: stopping the initially loaded 32 bit dbx and reloading the executable does not work, it gives the same problem: dbx: 32-bit dbx can't debug 64-bit app
-
The only workaround I found is to make the 32 bit dbx in OracleDeveloperStudio12.6-linux-x86-bin/developerstudio12.6/lib/dbx/32 unavailable, e.g. rename it
mv OracleDeveloperStudio12.6-linux-x86-bin/developerstudio12.6/lib/dbx/32/dbx OracleDeveloperStudio12.6-linux-x86-bin/developerstudio12.6/lib/dbx/32/dbx.bak
Which is fine with me as I do not intend to debug 32 bit applications anyway. But I'd still like to know whether there's a more convenient option.