-
Notifications
You must be signed in to change notification settings - Fork 70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
segmentation fault on bootstrap #31
Comments
Sorry this is the correct trace herc =====> ipl /root/diso/d390.ins |
It would help to know what exact version of Hyperion (which specific commit) you are reporting this error for. :) Your stack trace does not provide enough information to allow me to state with any high degree of confidence whether or not the problem you are reporting is being caused by commit fb3c2d1 made on August 4, 2014 (which introduced a serious bug into scedasd.c), but I find it quite likely. If it is, the bug in question was fixed by commit fcfa82a made a few days later on August 9, 2014, so until I learn otherwise I am going to go ahead and close this issue as having already been resolved. If the version of Hyperion you are (were) using already included (includes) the previous mentioned commit however, then please let me know or simply re-open this GitHub issue and I'll try to look into your issue a little deeper. Thank you for taking the time to report it and I apologize for having introduced the bug in the first place. |
Hi sorry for the delay (deserved holiday in progress). In the test i used the version of hercules hyperion master of 13 Aug. |
One thing we must know is the exact version of Hercules you are using. What does Hercules report when you enter the "version" Hercules command? I'm mostly a Windows developer, so I do not know how to debug segfaults on Linux. I'm guessing we probably need some type of "core" dump? Or maybe a more detailed stack trace? Maybe one of the other Hercules developers who knows Linux will help us? Help! :) |
To debug Hercules on unix:
When a core file is produced (where and under what name depends on the Be warned that Hercules uses a multitude of threads. On 09/01/2014 10:12 AM, Fish-Git wrote:
|
What does your /root/diso/d390.ins file look like? May we see your /root/diso/d390.ins file? What MAINSIZE are you using in your Hercules configuration file? |
The d390.ins the installation file of debian MAINSIZE is 6144 I recompiled hercules with your option and modified ulimit with your indication. Same result |
Sorry: Hercules version 4.00 |
Hello liviobait! I apologize for the delay. Do you prefer to be called "liviobait"? Or do you have a real name? :) Thank you for the Debian " Also, I still need to know the EXCACT version of Hercules that you are using. Telling me "4.00" does not help me. I need to see the output of the Hercules "
The above information is what I need to know! It tells me the exact version you are using and what build options were used. The first It might also be helpful to see your complete Hercules configuration file too. Knowing which *nix distribution you are using (i.e. which *nix you are running Hercules on) might also be helpful. IN SUMMARY:
Thank you! Fish |
Hi HHC01413I Hercules version 4.00 For config file CPU Configuration#------------------------------------------------------------------------------ CPUSERIAL 002623 # CPU serial number #------------------------------------------------------------------------------ OS Tailoring#------------------------------------------------------------------------------ LOADPARM 0120.... # IPL parameter TZOFFSET 0 # Using UTC (GMT)#------------------------------------------------------------------------------ Hercules Service Processor and Hercules Application Window#------------------------------------------------------------------------------ CODEPAGE default # CodePage conversion table HTTPPORT 8081 noauth #userid password # HTTP server port PANRATE FAST # Panel refresh rate #------------------------------------------------------------------------------- Integrated Hercules I/O ControllerDEVTMAX 0 # Device threads, 8 on Windows, else unlimitedCNSLPORT 3270 # TCP port number to which consoles connect SHRDPORT 3990 # TCP port number for sharing DASD images on
.-----------------------Device number| .-----------------Device type| | .---------File name and parameters| | |V V V---- ---- --------------------0009 3215-C / noprompt For system running hercules: Tank yuo! |
Thank you. I have downloaded it I will try it and then get back to you. (am very busy with other things too!) |
Resolved by commit# ed1ff43 Issued closed. "Fish" (David B. Trout) |
Hi
I have segmentation fault on ipl the debian installation.
ipl s390.ins (is the file for ipl installation) segfault.
This is the trace. If you need other information, just ask.
Tank you
(gdb) bt
#0 0x00007ffff76bd822 in s390_load_main (fname=0x7ffffffeec00 "/root/diso/boot/linux_vm", startloc=, noisy=0)
#1 0x00007ffff76be278 in s390_load_hmc (fname=0x7ffffffefc0b "vm", cpu=, clear=) at scedasd.c:214
#2 0x00007ffff7810bdd in ipl_cmd2 (argc=, argv=0x7fffffff0e90, cmdline=, clr_prm=)
#3 0x00007ffff781a29b in CallHercCmd (argc=2, argv=0x7fffffff0e90, cmdline=0x610a10 "ipl /root/diso/d390.ins") at cmdtab.c:400
#4 0x00007ffff781a343 in HercCmdLine (pszCmdLine=0x6119c0 "ipl") at cmdtab.c:456
#5 0x00007ffff781be4c in panel_command_r (cmdline=) at cmdtab.c:854
#6 0x00007ffff759ce97 in do_panel_command (cmd=) at panel.c:728
#7 0x00007ffff75a0217 in panel_display_r () at panel.c:3123
#8 0x00007ffff758bfc7 in impl (argc=, argv=) at impl.c:1136
#9 0x0000000000400fd0 in main (ac=1, av=0x7fffffffe708) at bootstrap.c:36
The text was updated successfully, but these errors were encountered: