This is the mail archive of the
gdb@sourceware.cygnus.com
mailing list for the GDB project.
Re: gdb seg violation during print command (more info)
- To: dan at cgsoftware dot com
- Subject: Re: gdb seg violation during print command (more info)
- From: David Cogen <cogen at ll dot mit dot edu>
- Date: Fri, 5 May 2000 16:42:57 -0400 (EDT)
- CC: kettenis at wins dot uva dot nl, gdb at sourceware dot cygnus dot com, cogen at poblano
> 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