This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
| Other format: | [Raw text] | |
Hi - On Thu, Jun 19, 2003 at 11:16:25AM +1000, Eyal Lebedinsky wrote: > When debugging a wrapper I often hit a problem when I register > an objects incorrectly. This almost always leads to a failure at > unregister time in mf-runtime.c in > assert (old_obj->data.type >= 0 && > old_obj->data.type <= __MF_TYPE_MAX_CEM); > I find it usefull to add a violation message at this point [...] If these bad objects enter the system from bad calls to __mf_register, I'd rather catch them there. Objects with a bad .type field should not be permitted to circulate in the database at all, never mind just at unregister time. > What is the current procedure for me submitting a patch - > gcc-patches list? [...] Send to gcc-patches (including ChangeLog etc.) and cc: me if you like. - FChE
Attachment:
pgp00000.pgp
Description: PGP signature
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |