I'm going crazy. For some reason, when I run the PL/SQL debugger through SQL Developer, setting a breakpoint anywhere in my package won't break -- but only on one database. If I use the same SQL Developer with the same settings on another 11.2.0.3 database on the same Linux server with the same package with a breakpoint in the same place, it breaks fine. If (on the database that doesn't work), I set the "Start Debugging Option" to "Step Into" and debug, the anonymous block window appears, the debugger starts on the first line of it, and I can "step into" through the anonymous block until it gets to the package's procedure, at which point it just runs through the procedure without stopping at any breakpoint. It isn't specific to the one package; trying to set a breakpoint in other packages doesn't work either.
So is there a trace or database-level setting that could be affecting this?
Settings: SQL Developer 4.1.3.20. I have a debugging port range set (if I don't, I get timeout errors on whatever random port it picks), so I don't think it's that. Besides, if it was a poor port, I don't think the anonymous block debugging would work. I tried setting "prompt for debugger host" and entering my PC's IP; no effect. I tried the different "start debugging option"s; no effect. I tried changing my database connection to use "basic" instead of "TNS"; no effect. And yeah, I've "compiled for debugging" on both the package and package body, and often. Thanky.