Doesn't "install" under windows

[techtonik]

./configure - ok
./make - fail

$ make
depbase=`echo src/processor/basic_code_modules.lo | sed 's|[^/]*
$|.deps/&|;s|\.lo$||'`; \
if /bin/sh ./libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -
I. -I./src -I./src -g -O2 -MT src/processor/basic_code_modules.lo -
MD -MP -MF "$depbase.Tpo" -c -o src/processor/basic_code_modules.lo
src/processor/basic_code_modules.cc; \
then mv -f "$depbase.Tpo" "$depbase.Plo"; else rm -f "$depbase.Tpo";
exit 1; fi
mkdir src/processor/.libs
g++ -DHAVE_CONFIG_H -I. -I. -I./src -I./src -g -O2 -MT src/processor/
basic_code_modules.lo -MD -MP -MF src/processor/.deps/
basic_code_modules.Tpo -c src/processor/basic_code_modules.cc -
DDLL_EXPORT -DPIC -o src/processor/.libs/basic_code_modules.o
g++ -DHAVE_CONFIG_H -I. -I. -I./src -I./src -g -O2 -MT src/processor/
basic_code_modules.lo -MD -MP -MF src/processor/.deps/
basic_code_modules.Tpo -c src/processor/basic_code_modules.cc -o src/
processor/basic_code_modules.o >/dev/null 2>&1
depbase=`echo src/processor/basic_source_line_resolver.lo | sed 's|
[^/]*$|.deps/&|;s|\.lo$||'`; \
if /bin/sh ./libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -
I. -I./src -I./src -g -O2 -MT src/processor/
basic_source_line_resolver.lo -MD -MP -MF "$depbase.Tpo" -c -o src/
processor/basic_source_line_resolver.lo src/processor/
basic_source_line_resolver.cc; \
then mv -f "$depbase.Tpo" "$depbase.Plo"; else rm -f "$depbase.Tpo";
exit 1; fi
g++ -DHAVE_CONFIG_H -I. -I. -I./src -I./src -g -O2 -MT src/processor/
basic_source_line_resolver.lo -MD -MP -MF src/processor/.deps/
basic_source_line_resolver.Tpo -c src/processor/
basic_source_line_resolver.cc -DDLL_EXPORT -DPIC -o src/
processor/.libs/basic_source_line_resolver.o
src/processor/basic_source_line_resolver.cc: In static member function
`static bool
google_breakpad::BasicSourceLineResolver::Module::Tokenize(char*, int,
std::vector<char*, std::allocator<char*> >*)':
src/processor/basic_source_line_resolver.cc:373: error: `strtok_r'
undeclared (first use this function)
src/processor/basic_source_line_resolver.cc:373: error: (Each
undeclared identifier is reported only once for each function it
appears in.)
make: *** [src/processor/basic_source_line_resolver.lo] Error 1

Is it possible to make breakpad compilable under MSYS/MinGW?

--
--t.

[techtonik]

Hello,

I've managed to compile breakpad processor under windows using MinGW.
I've posted hack into group files. I've managed to get dump reader
working and producing the same results as in testdata/. I've also
received a stack trace from stackwalker with and without symbols, but
only for machine readable format. In default mode it crashes itself
while trying to list modules.

...
Loaded modules:
0x00400000 - 0x00000000 ¤ f╟ (null)test_app.exe

However, I was unable to compile any client code. Unfortunately.

$ g++ test_app.cc
In file included from test_app.cc:38:
client/windows/handler/exception_handler.h:64:21: DbgHelp.h: No such
file or directory
In file included from test_app.cc:38:
client/windows/handler/exception_handler.h:161: error: `MINIDUMP_TYPE'
has not been declared
client/windows/handler/exception_handler.h:162: error: expected `,' or
`...' before "ExceptionParam"
client/windows/handler/exception_handler.h:164: error: ISO C++ forbids
declaration of `DumpType' with no type
client/windows/handler/exception_handler.h:164: error: ISO C++ forbids
declaration of `PMINIDUMP_EXCEPTION_INFORMATION' with no type

I really would like to see breakpad working with MinGW tools as they
are invaluable for cross-compilation.

--
--anatoly t.

[Mark Mentovai]

The exception_handler requires DbgHelp.h, which I understand isn't
available under mingw or isn't included in its equivalent of the
Platform SDK.

Mark

[Ted Mielczarek]

Will this be fixed if Issue 76 is fixed? Or are there other issues
blocking mingw support?

http://code.google.com/p/google-breakpad/issues/detail?id=76 --
"Windows 2000 support: Windows minidump writer without DbgHelp!
MiniDumpWriteDump"

Additionally, I assume there will still be problems with dump_syms.
What format does mingw use for debugging info?

-Ted

On Feb 26, 1:45 pm, "Mark Mentovai" <mmento...@gmail.com> wrote:
> The exception_handler requires DbgHelp.h, which I understand isn't
> available under mingw or isn't included in its equivalent of the
> Platform SDK.
>
> Mark
>

[Brian Ryner]

I'd guess it uses stabs or dwarf, and if that's the case, you might be able to leverage the mac or linux symbol dumpers.

[Mark Mentovai]

We'd certainly accept a symbol dumper port that works with mingw or
cygwin compilers.

Mark