Breakpoints have now been patented

An anonymous reader noted that apparently Breakpoints have now been patented. From the link "A method for debugging including the steps of receiving code having a software breakpoint function therein, running the code for the purpose of debugging, monitoring the code to detect the presence of the software breakpoint function, recognizing the software breakpoint function, determining an action to be performed based on the software breakpoint function, and implementing the action. The present invention also includes an apparatus for implementing the method for debugging and a medium embodying a program of instructions for execution by a device to perform the method for debugging."

Comments

Could someone please patent code comments?

[Anonymous Coward]

I'd love to have this as an excuse for not doing them. Thanks.

Re:Could someone please patent code comments?

[SL Baur]

No that's not what they've patented. They've patented source level debugging with static break points. Apparently the developer litters the source code with SOFTWARE_BREAKPOINT; calls which turn into do-nothing statements if there is no debugger running the code. The target environment appears to be an embedded system like a cellphone.

They have not patented hardware breakpoints, gdb, etc. and a huge advantage of their system is that you could apparently debug and selectively enable/disable breakpoints in a production ROM executable image.

I know noone reads these patents when these kinds of articles go by, this is /., but is it too much to ask that the article submitter or the editor read them first?

Re:Could someone please patent code comments?

[keird]

Visual Basic has had this for years. It's called Stop. When running in the IDE execution breaks at the Stop command just as if you had a breakpoint defined. The command does nothing when running outside of the IDE.

Next up...

[CdrGlork]

Next to be patented will be the GOTO statement, so ALL YOU LAZY PROGGERS WILL STOP USING IT!

Re:Next up...

[Vihai]

I DO use gotos heavily.

If you know where and how to use them, they actually are a sensible choice.

They are very good in implementing the function rollback code, that is code which has to undo everything the function has done in case of an error.

For example:

int allocstuff(void)
{
        char *a = malloc(100);
        if (!a)
                goto err_malloc_a;

        char *b = malloc(100);
        if (!b)
                goto err_malloc_b;

        return 0;

        free(b);
err_malloc_b:
        free(a);
err_malloc_a:

        return -1;
}

Re:Next up...

[Dachannien]

Your code makes me want to throw up.

That's it.

[Manos_Of_Fate]

I'm applying for a patent on "A system of tubes, that carries information globally, so as to assist the procurement of pr0n."

hardware debugger

[Anonymous Coward]

its a hardware debugger or so it appears, not a software one, they specifically address pitfalls with software debuggers and why they did this method.

while hardware ones arent totally new, they arent that common either. gdb is immune from this for example since its software only.

the abstract isnt the patent, the title isnt the patent, the claims are the patent. Readers are encouraged to read the claims and not spread FUD because they can.

Re:I think this is a bit different

[escay]

From what I understand (read the invention background section in the patent) This is a patent about the implementation of a breakpoint handling mechanism, not the idea of using breakpoints to debug itself. specifically, conventional breakpoint sends a software interrupt that is either caught by (a) the debugger, pausing/halting program execution or (b) the OS, in case no debugger is present, resulting in a system hang or crash. Also the assembly halt code may vary for different processors.

The patented breakpoint function catches interrupts and handles them in a specific way, irrespective of whether a debugger is running or not, and also issues CPU-indepedent halt codes, marking an improvement over existing techniques.

Karma whoring, you say? I just have a fascination for patents.

Step 2?

[fishdan]

Step 1: Patent commenting
Step 2: ???????????
Step 3: Profit!!!!

The problem is there will be no profit because no one comments. On the other hand, at least there is no prior art to rule against your patent.