Issue 330 in google-breakpad: linux_syscall_support.h has extra semicolons causing compilation to fail with certain gcc options

11 views
Skip to first unread message

codesite...@google.com

unread,
Aug 27, 2009, 4:44:48 PM8/27/09
to google-brea...@googlegroups.com
Status: New
Owner: ----

New issue 330 by joshmoz: linux_syscall_support.h has extra semicolons
causing compilation to fail with certain gcc options
http://code.google.com/p/google-breakpad/issues/detail?id=330

linux_syscall_support.h has some extra semicolons in it:

/builds/slave/sendchange-linux-hg/build/toolkit/crashreporter/google-breakpad/src/client/../common/linux/linux_syscall_support.h:2128:
error: extra ‘;’
/builds/slave/sendchange-linux-hg/build/toolkit/crashreporter/google-breakpad/src/client/../common/linux/linux_syscall_support.h:2131:
error: extra ‘;’
/builds/slave/sendchange-linux-hg/build/toolkit/crashreporter/google-breakpad/src/client/../common/linux/linux_syscall_support.h:2771:
error: extra ‘;’


Attachments:
upstream1.patch 1.6 KB

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

codesite...@google.com

unread,
Aug 27, 2009, 6:51:11 PM8/27/09
to google-brea...@googlegroups.com
Updates:
Cc: nealsid

Comment #1 on issue 330 by mmentovai: linux_syscall_support.h has extra

semicolons causing compilation to fail with certain gcc options
http://code.google.com/p/google-breakpad/issues/detail?id=330

Josh, I don't see where the extra semicolons are coming from. Is there
some sort of
non-obvious macro at work here?

codesite...@google.com

unread,
Aug 27, 2009, 7:06:19 PM8/27/09
to google-brea...@googlegroups.com

Comment #2 on issue 330 by joshmoz: linux_syscall_support.h has extra
semicolons causing compilation to fail with certain gcc options
http://code.google.com/p/google-breakpad/issues/detail?id=330

I don't know, at a glance it just looks like someone made a copy/paste
error to me. I
didn't actually read into the code.

Reply all
Reply to author
Forward
0 new messages