gdb seg violation during print command (more info)

[David Cogen]

> They are, we ignore the argument names completely.
> Which is why i claim it's not gdb's fault.
> It's the compiler telling gdb it's an int (void), not gdb.
> --Dan

But I still must pass an int to a function declared int (int), not only to a
function declared int (int arg), for the function to compile. Omitting "arg"
is just telling the compiler that the argument is not used, so not to generate
a "not used" warning.

Should I pursue this as a gcc bug?


-- DavidC