All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Toralf Förster" <toralf.foerster@gmx.de>
To: trinity@vger.kernel.org
Subject: Re: latest git tree core dumps
Date: Wed, 19 Feb 2014 22:16:52 +0100	[thread overview]
Message-ID: <53051F44.1040205@gmx.de> (raw)
In-Reply-To: <53051646.8060706@gmx.de>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

hhm - solved in 3d79afa..da55d79

On 02/19/2014 09:38 PM, Toralf Förster wrote:
> Under a 32 bnit user mode linux I do get :
> 
> Core was generated by `trinity -q -N 10000 -C 8 -x move_pages -x
> mremap'. Program terminated with signal 11, Segmentation fault. #0
> 0x0804d870 in output (level=level@entry=0 '\000', 
> fmt=fmt@entry=0x805fcdc "Marking syscall %s (%d) as to be
> %sabled.\n") at log.c:306 306     log.c: No such file or
> directory.
> 
> 
> (gdb) (gdb) (gdb) (gdb) bt full #0  0x0804d870 in output
> (level=level@entry=0 '\000', fmt=fmt@entry=0x805fcdc "Marking
> syscall %s (%d) as to be %sabled.\n") at log.c:306 args =
> <optimized out> n = 0 handle = <optimized out> pid = 5469 outputbuf
> =
> "\320\316\000\000\b\001\000\000\b\001\000\000\006\000\000\000\004\000\000\000\004\000\000\000t\001\000\000t\001\000\000t\001\000\000
> \000\000\000
> \000\000\000\004\000\000\000\004\000\000\000P\345td̚\000\000̚\000\000̚\000\000<\003\000\000<\003\000\000\004\000\000\000\004\000\000\000Q\345td",
> '\000' <repeats 16 times>,
> ")\201\000@\300\017\002@\270\306ۿ\000\000\000\000\350\306ۿn\313\000@\000\000\000\000\000\000\000\200\000\000\000\000\004\000\000\000\001\000\000\000\000\000\000\000\b\000\000\000\356\356\000@\270\306ۿ\000\000\000\000\000\000\000\000\000(\000\000p\030\002@\264\306ۿ\260\306ۿ-\216\000@\361\363\003@L(
> @\002\000\000\000\000\000\000\000\020\000\000\000X4\035@\240\371\001\000s\037i\t\006(
> @\350\033\002@,\000\000\000\300\017\002@\244\375\002"... prefix =
> 0xbfdbc362 "[init]" watchdog_prefix = "[watchdog]" init_prefix =
> "[init]" main_prefix = "[main]" child_prefix =
> "[childNN:1234567890]" #1  0x0805326c in toggle_syscall_n
> (calln=317, state=state@entry=FALSE, arg=arg@entry=0xbfdbceab
> "move_pages", arg_name=arg_name@entry=0xbfdbceab "move_pages") at
> tables-uniarch.c:51 entry = 0x40269030 #2  0x08053dc3 in
> toggle_syscall (arg=0xbfdbceab "move_pages",
> state=state@entry=FALSE) at tables.c:299 specific_syscall =
> <optimized out> arg_name = 0xbfdbceab "move_pages" #3  0x0804f1ef
> in parse_args (argc=argc@entry=10, argv=argv@entry=0xbfdbcd84) at
> params.c:340 ---Type <return> to continue, or q <return> to
> quit--- opt = <optimized out> #4  0x0804a3c3 in main (argc=10,
> argv=0xbfdbcd84) at trinity.c:76 ret = 0 childstatus = 1073878300 
> pid = <optimized out> taskname = "trinity-main" (
> 
> 
> 
> 

- -- 
MfG/Sincerely
Toralf Förster
pgp finger print:1A37 6F99 4A9D 026F 13E2 4DCF C4EA CDDE 0076 E94E
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iF4EAREIAAYFAlMFH0QACgkQxOrN3gB26U6ZZwD+JCtwke59hVEONNej39TYIY2l
01UWbGneu2x4iz57cJUA/31iYaTUJ0cZv+9wShBBy8ojVJtmehK1DrQPj5ehlVvV
=6ibz
-----END PGP SIGNATURE-----

      reply	other threads:[~2014-02-19 21:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-19 20:38 latest git tree core dumps Toralf Förster
2014-02-19 21:16 ` Toralf Förster [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=53051F44.1040205@gmx.de \
    --to=toralf.foerster@gmx.de \
    --cc=trinity@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.