Re: [Monotone-devel] fatal: memory access violation running mtn log
Hi! Danny MacMillan pisze: Hi, I just got an error using monotone. What I did was basically follow the cut Revision: 045b0286268ed071e6ac83bc87cdcb751b38718f cut C:\Program Files\monotone\mtn.exe: fatal: memory access violation this is almost certainly a bug in monotone. please send this error message, the output of 'C:\Program Files\monotone\mtn.exe version --full', and a description of what you were doing to monotone-devel@nongnu.org cut Thanks for report! This error is reproducible on other machines. I am analyzing the cause. Failing test case (on nvm workspace): mtn log --from 045b0286268ed071e6ac83bc87cdcb751b38718f fails also here, but in somewhat different place (maybe it's a buffering problem?): | o - | | Revision: 8313738ccc7884cf79fb1b3b66fe418f61b1e07a | | Ancestor: 184259296d94033bb62d0775bb0288efefe917d1 | | Author: Richard Levitte rich...@levitte.org | | Date: 2009-01-15 14:45:31 | | Branch: net.venge.monotone | | | | Modified files: | | contrib/display_branches.lua | | | | ChangeLog: | | | | * contrib/display_branches.lua: Modernised version. Program received signal SIGSEGV, Segmentation fault. And for the rest - here is the backtrace: 0x007d120e in date_t::as_formatted_localtime (this=0x22ea48, f...@0x22f6d0) at ../net.venge.monotone/dates.cc:367 367 tm tb(*std::localtime(t)); (gdb) bt #0 0x007d120e in date_t::as_formatted_localtime (this=0x22ea48, f...@0x22f6d0) at ../net.venge.monotone/dates.cc:367 #1 0x004d6525 in log_date_certs (cer...@0x22f0e0, o...@0x22f000, f...@0x22f6d0, label=0xc41c4e Date: , separator=0xc41c4e Date: , multiline=false, newline=true) at ../net.venge.monotone/vocab_terms.hh:618 #2 0x004e158a in commands::cmd_log::exec (this=0xcd17a0, a...@0x22fb10, exec...@0x22fad0, ar...@0x22fb10) at ../net.venge.monotone/cmd_diff_log.cc:697 #3 0x00476a9b in commands::process (a...@0x22fb10, ide...@0x22fad0, ar...@0x22fb10) at ../net.venge.monotone/cmd.cc:118 #4 0x0080e195 in cpp_main (argc=4, argv=0x3e4a68) at ../net.venge.monotone/monotone.cc:285 #5 0x0080ea1b in main (argc=4, argv=0x3e4a68) at ../net.venge.monotone/win32/main.cc:198 (gdb) Best regards! -- Zbigniew Zagórski / software developer / geek / http://zbigg.blogspot.com / ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
Re: [Monotone-devel] fatal: memory access violation running mtn log
Hello! Zbigniew Zagórski wrote: Hi! Danny MacMillan pisze: Hi, I just got an error using monotone. What I did was basically follow the cut Revision: 045b0286268ed071e6ac83bc87cdcb751b38718f cut C:\Program Files\monotone\mtn.exe: fatal: memory access violation this is almost certainly a bug in monotone. please send this error message, the output of 'C:\Program Files\monotone\mtn.exe version --full', and a description of what you were doing to monotone-devel@nongnu.org cut Thanks for report! This error is reproducible on other machines. I am analyzing the cause. Failing test case (on nvm workspace): mtn log --from 045b0286268ed071e6ac83bc87cdcb751b38718f fails also here, but in somewhat different place (maybe it's a buffering problem?): Hello! OK, problem identified. Someone/somewhere had misconfigured machine (?) and thus generated weird date cert: $ mtn ls certs cdf1680ec496d22f863184a cut Key : tbrow...@gmail.com (475055ec71...) Sig : ok Name : date Value : 1969-12-25T17:04:08 ^^^ and looks like localtime on woe32 can't cope with this - thus returning 0 from localtime call. Recap: failing test case: $ mtn log --from cdf1680ec496d22f863184a --last 1 -- Zbigniew Zagórski / software developer / geek / http://zbigg.blogspot.com / ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
Re: [Monotone-devel] fatal: memory access violation running mtn log
Zbigniew Zagórski wrote: OK, problem identified. Someone/somewhere had misconfigured machine (?) and thus generated weird date cert: $ mtn ls certs cdf1680ec496d22f863184a cut Key : tbrow...@gmail.com (475055ec71...) Sig : ok Name : date Value : 1969-12-25T17:04:08 ^^^ date.cc works in milliseconds. There's a place where about a year ago it was multiplying a time_t by 1000 without a cast to an explicit 64-bit type, and I was apparently the first to use this on a 32-bit machine. ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] fatal: memory access violation running mtn log
Hi, I just got an error using monotone. What I did was basically follow the instructions in the INSTALL file to init a new database and pull the net.venge.monotone branch into it, check out the branch into a new directory, and run mtn log. That is: mtn --db=mt.mtn db init mtn --db=mt.mtn pull monotone.mtn-host.prjek.net net.venge.monotone mtn --db=mt.mtn --branch net.venge.monotone co mt cd mt mtn log Approximately a brazillion lines of text later, I get the following (I stripped the vertical pipes at the beginning of the log lines to prevent wrapping). It is repeatable, it always happens at just this point in the log output. I nuked my mt.mtn file and the mt directory and repeated the process, and I am getting exactly the same result. - Revision: 045b0286268ed071e6ac83bc87cdcb751b38718f Ancestor: cdf1680ec496d22f863184a1fae75ef43bbbe6fc Ancestor: f8cbaacd6172e24de840a4b9326ca1ed58a92f54 Author: Timothy Brownawell tbrow...@gmail.com Date: 2009/01/17 10:29:43 Added files: origin_type.hh Modified files: Makefile.am annotate.cc asciik.cc automate.cc basic_io.cc basic_io.hh cert.cc cert.hh charset.cc charset.hh cmd.hh cmd_automate.cc cmd_conflicts.cc cmd_db.cc cmd_diff_log.cc cmd_files.cc cmd_key_cert.cc cmd_list.cc cmd_merging.cc cmd_netsync.cc cmd_othervcs.cc cmd_packet.cc cmd_ws_commit.cc commands.cc contrib/display_branches.lua crypto_tests.cc cset.cc database.cc database_check.cc dates.cc diff_patch.cc epoch.cc file_io.cc globish.cc globish.hh graph.cc inodeprint.cc key_store.cc keys.cc legacy.cc lua.cc lua.hh lua_hooks.cc lua_hooks.hh luaext_globish.cc luaext_guess_binary.cc luaext_mkstemp.cc luaext_parse_basic_io.cc luaext_platform.cc merge.cc merkle_tree.cc monotone.cc mt_version.cc netcmd.cc netsync.cc netxx_pipe.cc option.cc option.hh options_list.hh packet.cc paths.cc paths.hh pcrewrap.cc pcrewrap.hh po/it.po project.cc rcs_import.cc refiner.cc restrictions.cc revision.cc roster.cc roster_delta.cc roster_merge.cc safe_map.hh sanity.cc sanity.hh schema_migration.cc selectors.cc sha1.cc simplestring_xform.hh ssh_agent.cc std_hooks.lua tester.cc tests/commit_validation_lua_hook/__driver__.lua tests/resolve_conflicts_errors/__driver__.lua tests/two_parent_workspace_commands_that_fail/__driver__.lua transforms.cc transforms.hh ui.cc ui.hh unix/fs.cc unix/process.cc unix/ssh_agent_platform.cc unix/tester-plaf.cc uri.cc uri.hh vocab.cc vocab_cast.hh vocab_macros.hh win32/fs.cc win32/ssh_agent_platform.cc win32/tester-plaf.cc work.cc work_migration.cc xdelta.cc ChangeLog: Propagate nvm to nvm.error-handling. C:\Program Files\monotone\mtn.exe: fatal: memory access violation this is almost certainly a bug in monotone. please send this error message, the output of 'C:\Program Files\monotone\mtn.exe version --full', and a description of what you were doing to monotone-devel@nongnu.org C:\Documents and Settings\danm\mtmtn version --full monotone 0.46 (base revision: e282b2cf8b86caf828930b3b1ec67f41153084e4) Running on : Windows NT/2000/XP/2003 (5.1, build 2600, Service Pack 3) on ia32 (level 6, rev 3851) C++ compiler: GNU C++ version 3.4.5 (mingw-vista special r3) C++ standard library: GNU libstdc++ version 20051201 Boost version : 1_39 SQLite version : 3.6.7 (compiled against 3.6.7) Lua version : Lua 5.1 PCRE version: 7.8 2008-09-05 (compiled against 7.9) Botan version : 1.8.8 (compiled against 1.8.8) Changes since base revision: format_version 1 new_manifest [8204149c6fac0ae884996f2f015a70bfa127b7b5] old_revision [e282b2cf8b86caf828930b3b1ec67f41153084e4] ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
